Malicious code in debug
Published 8 Sept 2025 · Updated 16 Sept 2025
Remove this package
Installing an affected version can run code that steals tokens and keys. Remove it, then rotate any secrets that were on the machine or CI runner that installed it.
Affected package
- Affected
- 4.4.2
- Fixed in
- No fix released
Details
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.
Is MAL-2025-46974 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected debug, and gives you the command that fixes it.
References
- Articlewww.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
- Articlewww.bleepingcomputer.com/news/security/hackers-hijack-npm-packages-with-2-billion-weekly-downloads-in-supply-chain-attack/
- Linkgithub.com/github/advisory-database/issues/6099
- Advisorygithub.com/advisories/GHSA-8mgj-vmr8-frr6
- Linkgithub.com/debug-js/debug/security/advisories/GHSA-4x49-vf9v-38px
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.