{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59330 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-59330 is a high-severity vulnerability in Qix- node-error-ex, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59330 and fix it if it is affected.\n\nWhat it is: CVE-2025-59330 is a high-severity vulnerability in Qix- node-error-ex, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59330 in the wild and no public exploit code.\n\nAffected product: Qix- node-error-ex. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59330/ (Markdown: https://insights.sbomify.com/CVE-2025-59330/index.md)","id":"CVE-2025-59330","markdown":"https://insights.sbomify.com/CVE-2025-59330/index.md","name":"CVE-2025-59330","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"npm JavaScript library","requires_auth":"none","summary":"Attackers injected malware into an npm package to hijack cryptocurrency transactions in browser environments, requiring users to upgrade and rebuild bundles.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-506","name":"Embedded Malicious Code"}],"description":"error-ex allows error subclassing and stack customization. On 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. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct \u003cscript\u003e 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. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 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. Users 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. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 1.3.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"error-ex@1.3.3 contains malware after npm account takeover","id":"CVE-2025-59330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"is-arrayish@0.3.3 contains malware after npm account takeover","id":"CVE-2025-59331"},"packages":[],"prev":{"headline":"Apache Fory: Denial of Service (DoS) due to Deserialization of Untrusted malicious large Data","id":"CVE-2025-59328"},"products":["node-error-ex"],"published":"2025-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-15","vendors":["Qix-"]},"summary":"Attackers injected malware into an npm package to hijack cryptocurrency transactions in browser environments, requiring users to upgrade and rebuild bundles.","url":"https://insights.sbomify.com/CVE-2025-59330/"}