Malicious Code Injection in accused_haddock-notthedevs Package
Summary
MAL-2025-99096: Malicious code in accused_haddock-notthedevs (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The accused_haddock-notthedevs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious design of the accused_haddock-notthedevs package, which includes scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants, thus polluting the npm registry with potentially harmful packages. The ramifications include the risk of developers unknowingly using compromised packages, leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall accused_haddock-notthedevsIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the accused_haddock-notthedevs package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The accused_haddock-notthedevs package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert for ongoing monitoring of their applications.
See every vulnerability recorded for accused_haddock-notthedevs →
FAQ
It is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
You should uninstall the package immediately using 'npm uninstall accused_haddock-notthedevs' and check for any other affected packages.
Yes, using this package can lead to security vulnerabilities in your application due to the malicious modifications it makes to package metadata.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
