Malicious Code Injection in only_kangaroo-notthedev Package
Summary
MAL-2025-106732: Malicious code in only_kangaroo-notthedev (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 only_kangaroo-notthedev package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior is indicative of a broader issue within the npm ecosystem, where malicious actors exploit the platform for personal gain.
Vulnerability Detail
The vulnerability in the only_kangaroo-notthedev package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous malicious packages flooding the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall only_kangaroo-notthedev
If 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 remove the only_kangaroo-notthedev package from your project by executing the command: npm uninstall only_kangaroo-notthedev. This will prevent any malicious code from executing until a patched version is available.
Conclusion
The only_kangaroo-notthedev package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential to take immediate action by updating or uninstalling the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for only_kangaroo-notthedev →
FAQ
It is an npm package that is part of a campaign to inflate developer reputation scores by generating and publishing derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should immediately update or uninstall the package to prevent any potential security risks.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.