Malicious Code Injection in plastic_asp_z3n: A Threat to npm Packages
Summary
MAL-2025-95908: Malicious code in plastic_asp_z3n (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 plastic_asp_z3n is part of a series of npm packages associated with 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 poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability in plastic_asp_z3n originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall plastic_asp_z3nIf 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 plastic_asp_z3n package and any packages that depend on it. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The plastic_asp_z3n package poses a significant risk due to its malicious code that alters package.json files and repurposes the package for autopublishing. It is crucial to remove this package from your projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for plastic_asp_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and repurposes the package for autopublishing, leading to potential security risks.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help identify affected packages.
Uninstall the package immediately using 'npm uninstall plastic_asp_z3n' and check for any dependencies that may require it.
Yes, using this package can lead to the pollution of the npm registry and expose your project to security vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
