Malicious Code Injection in abangamad: A Threat to npm Ecosystem
Summary
MAL-2025-170619: Malicious code in abangamad (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 package 'abangamad' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry by generating numerous derivative packages, thereby inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'abangamad' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem. The malicious payload is designed to exploit the npm infrastructure, making it crucial for developers to be aware of this threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abangamadIf 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 'abangamad' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. 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 'abangamad' package poses a significant risk due to its malicious code that manipulates the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security and provide real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for abangamad →
FAQ
The 'abangamad' package is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should remove the 'abangamad' package from your project and monitor for any updates or patches.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just package-lock.json. You can check your application at Vulert Scanner.
Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to mitigate risks.
