Malicious Code Injection in loud_haddock-appteadev Package
Summary
MAL-2025-105332: Malicious code in loud_haddock-appteadev (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 loud_haddock-appteadev package is part of the npm ecosystem, commonly used for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package management system. This package is designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata, which can lead to reputation inflation and potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability originates from the package being linked to the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall loud_haddock-appteadevIf 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 measure, you can avoid using the loud_haddock-appteadev package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Conclusion
The loud_haddock-appteadev package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for loud_haddock-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to dependency confusion, potential exploitation, and pollution of the npm registry, affecting the integrity of your application.
You should remove the loud_haddock-appteadev package from your project and monitor for any updates or patches.
You can use Vulert to monitor your package-lock.json file for vulnerabilities without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.
