Malicious Code Injection in actual_haddock_dumbs Package - npm Vulnerability
Summary
MAL-2025-99101: Malicious code in actual_haddock_dumbs (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 actual_haddock_dumbs 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 capabilities. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward scheme. The package's functionality is compromised, making it a potential threat to users and developers alike.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the actual_haddock_dumbs package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The ramifications include the risk of executing malicious code, loss of control over package versions, and damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall actual_haddock_dumbsIf 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 actual_haddock_dumbs package by not including it in your dependencies. Additionally, consider using a package monitoring tool like Vulert, which can alert you to vulnerabilities in your dependencies. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The actual_haddock_dumbs package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial for developers to remove this package from their projects and utilize monitoring tools to safeguard against future vulnerabilities. By staying informed and proactive, developers can help maintain the integrity of the npm ecosystem.
See every vulnerability recorded for actual_haddock_dumbs →
FAQ
The actual_haddock_dumbs package is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing features.
This vulnerability can lead to the installation of compromised packages, execution of malicious code, and potential damage to your project's integrity.
You should uninstall the actual_haddock_dumbs package immediately using npm uninstall actual_haddock_dumbs and check your package-lock.json for any references.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Regularly update your dependencies, use vulnerability monitoring tools like Vulert, and audit your packages for known vulnerabilities.
