ua-parser-js Crypto Mining backdoor
Description
Compromised versions of ua-parser-js (0.7.29, 0.8.0, 1.0.0) contained a backdoor introducing unauthorized crypto-mining on affected systems.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Compromised versions of ua-parser-js (0.7.29, 0.8.0, 1.0.0) contained a backdoor introducing unauthorized crypto-mining on affected systems.
Vulnerability
Versions 0.7.29, 0.8.0, and 1.0.0 of the ua-parser-js npm package were found to contain a backdoor in the crypto mining component [1][2][3]. The package is a JavaScript library for user-agent detection, widely used in both client-side and Node.js environments. The compromised versions were hijacked and modified to include malicious code, affecting any application that installed these versions via npm.
Exploitation
An attacker with the ability to distribute the compromised npm packages (achieved through account hijacking) could cause exploitation. An end-user or developer who installed version 0.7.29, 0.8.0, or 1.0.0 would execute the malicious code during npm install or when the library was loaded. No additional authentication or user interaction beyond the install process is required. The backdoor specifically targets the crypto mining component, enabling unauthorized cryptocurrency mining on the infected host.
Impact
Successful exploitation results in unauthorized execution of a cryptocurrency miner on the affected system [1][2]. This can lead to resource exhaustion (CPU, memory, power), degraded system performance, and potential additional compromise if the miner communicates with external servers. The impact is rated as critical due to the stealthy nature of the backdoor and the potential for widespread use of the library.
Mitigation
The vulnerability is addressed in versions 0.7.30, 0.8.1, and 1.0.1 [1]. Users should immediately upgrade to these or later versions. For those unable to upgrade, a workaround is to pin the package version to a known safe version such as 0.7.28 or to use a different user-agent detection library. The compromised versions have been removed from npm, and the package maintainers have released patches. This CVE does not appear in the Known Exploited Vulnerabilities (KEV) catalog as of the publication date.
- GitHub - faisalman/ua-parser-js: UAParser.js - The Essential Web Development Tool for User-Agent Detection. Detect Browsers, OS, Devices, Bots, Apps, AI Crawlers, and more. Run in Browser (client-side) or Node.js (server-side).
- Security issue: compromised npm packages of ua-parser-js (0.7.29, 0.8.0, 1.0.0) - Questions about deprecated npm package ua-parser-js
- Security issue: compromised npm packages of ua-parser-js (0.7.29, 0.8.0, 1.0.0) - Questions about deprecated npm package ua-parser-js
AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
ua-parser-jsnpm | >= 0.7.29, < 0.7.30 | 0.7.30 |
ua-parser-jsnpm | >= 0.8.0, < 0.8.1 | 0.8.1 |
ua-parser-jsnpm | >= 1.0.0, < 1.0.1 | 1.0.1 |
Affected products
2- unspecified/ua-parser-jsv5Range: 0.7.29
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
5- github.com/advisories/GHSA-pjwm-rvh2-c87wghsax_refsource_MISCADVISORY
- github.com/faisalman/ua-parser-js/issues/536ghsax_refsource_MISCWEB
- github.com/faisalman/ua-parser-js/issues/536ghsaWEB
- vuldb.commitrex_refsource_MISC
- www.npmjs.com/package/ua-parser-jsghsaWEB
News mentions
0No linked articles in our index yet.