Malicious Code Injection in complex_possum_z3n: A Threat to npm Packages
Summary
MAL-2025-93682: Malicious code in complex_possum_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 'complex_possum_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'complex_possum_z3n' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security 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 complex_possum_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 measure, you can avoid using the 'complex_possum_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'complex_possum_z3n' package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.
See every vulnerability recorded for complex_possum_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, potentially compromising the security of applications that depend on affected packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without needing to sign up.
If you have installed this package, it is recommended to uninstall it immediately and review your project's dependencies for any other potentially malicious packages.
No, there are no patches available for this specific package. The best course of action is to remove it from your project.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor your project for vulnerabilities.
