Malicious code in debug (npm)
The package was compromised and malicious code added. --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (558d1dda312e85212121f4ed15340349f780f5e40d6685c3687648bbb2924381) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-59144US | — | — | ||
debug is a JavaScript debugging utility. On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-8mgj-vmr8-frr6ADVISORY
- https://github.com/debug-js/debug/security/advisories/GHSA-4x49-vf9v-38pxWEB
- https://github.com/github/advisory-database/issues/6099WEB
- https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromisedARTICLE
- https://www.bleepingcomputer.com/news/security/hackers-hijack-npm-packages-with-2-billion-weekly-downloads-in-supply-chain-attack/ARTICLE
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan