Malicious Code Injection in standard_possum-toolteadev: A Threat to npm Users
Summary
MAL-2025-109075: Malicious code in standard_possum-toolteadev (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 'standard_possum-toolteadev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in 'standard_possum-toolteadev' originates from malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks for developers who unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall standard_possum-toolteadevIf 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 'standard_possum-toolteadev' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'standard_possum-toolteadev' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to update or remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for standard_possum-toolteadev →
FAQ
The malicious code modifies package metadata and generates random package names to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
Using compromised packages can lead to security vulnerabilities, data breaches, and damage to your application's reputation.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security patches.
Remove the package from your project and update to a secure alternative. Ensure to audit your project for any other potential vulnerabilities.
