Vulnerabilities in pkg:npm/error-ex
PACKAGECVE-2025-59330 is a HIGH error-ex@1.3.3 contains malware after npm vulnerability (CWE-506: Embedded Malicious Code) affecting Error ex libraries in the npm ecosystem. The issue involves error-ex@1.3.3 contains malware after npm account takeover. Remediation is available by upgrading affected packages to version 1.3.4.
pkg:npm/error-ex
Vulnerability advisories affecting package pkg:npm/error-ex. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-6jp5-hh4c-8c5h | CVE-2025-59330 | HIGH | error-ex@1.3.3 contains malware after npm account takeover |
CVE-2025-59330 at a Glance
How to Fix CVE-2025-59330
To remediate this vulnerability, upgrade all affected Error ex dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install error-ex@1.3.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls error-ex
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-59330, inspect your project dependencies using npm:
npm ls error-ex
Analyze the terminal output to locate any version of Error ex in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.4), your application is affected.
Note: The npm ls error-ex command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Error ex, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-59330 Affected Error ex Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
error-ex
|
npm |
≥ 1.3.3
< 1.3.4
All 1 versions
1.3.3
|
1.3.4
|
References
Frequently Asked Questions
What is CVE-2025-59330?
Which Error ex versions are affected?
What version fixes CVE-2025-59330?
Is error-ex affected?
What CWE is associated with CVE-2025-59330?
How can I check npm dependencies for CVE-2025-59330?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-6jp5-hh4c-8c5h",
"modified" : "2025-09-15T23:58:04Z",
"published" : "2025-09-15T23:58:03Z",
"aliases" : [ "CVE-2025-59330" ],
"summary" : "error-ex@1.3.3 contains malware after npm account takeover",
"details" : "### Impact\nOn 8 September 2025, an npm publishing account for `error-ex` was taken over after a phishing attack. Version `1.3.3` was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.\n\nLocal environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct `<script>` inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.\n\nThe malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.\n\n### Patches\nnpm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.\n\nOn 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.\n\nUsers should update to the latest patch version, completely remove their `node_modules` directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.\n\nThose operating private registries or registry mirrors should purge the offending versions from any caches.\n\n### References\n- https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised\n- https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack\n- https://www.ox.security/blog/npm-packages-compromised/\n\n### Point of Contact\nIn the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see _Patches_ above), please reach out via one of the following channels of communication:\n\n- Bluesky, compromised publishing account owner: https://bsky.app/profile/bad-at-computer.bsky.social\n- `debug` repository, tracking issue (applies to all packages affected in the breach): https://github.com/debug-js/debug/issues/1005",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:A/U:Red"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "error-ex"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.3.3"
}, {
"fixed" : "1.3.4"
} ]
} ],
"versions" : [ "1.3.3" ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Qix-/node-error-ex/security/advisories/GHSA-6jp5-hh4c-8c5h"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-59330"
}, {
"type" : "WEB",
"url" : "https://github.com/debug-js/debug/issues/1005"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Qix-/node-error-ex"
}, {
"type" : "WEB",
"url" : "https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack"
}, {
"type" : "WEB",
"url" : "https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised"
}, {
"type" : "WEB",
"url" : "https://www.ox.security/blog/npm-packages-compromised"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-506" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-09-15T23:58:03Z",
"nvd_published_at" : "2025-09-15T20:15:39Z"
}
}