Malicious Code Injection in sensible_asp_z3n Package - npm Vulnerability
Summary
MAL-2025-96516: Malicious code in sensible_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 sensible_asp_z3n package 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 the proliferation of malicious packages designed to manipulate the npm registry. The package's primary function is to facilitate the distribution of code, but it has been compromised to include harmful scripts that can affect developers and their projects.
Vulnerability Detail
The vulnerability in the sensible_asp_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which incentivizes the creation of derivative packages to inflate developer reputation scores. The ramifications include potential security risks for developers using this package, as it can lead to unauthorized access and manipulation of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sensible_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 remove the sensible_asp_z3n package from your project by executing the following command: npm uninstall sensible_asp_z3n. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The sensible_asp_z3n package has been identified as containing malicious code that poses a significant risk to developers using it. Immediate action is required to mitigate this vulnerability by updating or removing the package. Utilizing tools like Vulert can help in monitoring and preventing such vulnerabilities in the future.
See every vulnerability recorded for sensible_asp_z3n →
FAQ
The vulnerability involves malicious code that alters package.json files and generates random package names, leading to npm registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
If you have installed the vulnerable package, you should uninstall it immediately and check for any updates or patches.
While specific exploits have not been detailed, the malicious nature of the code poses significant risks to developers and their projects.
Regularly update your packages, use tools like Vulert for monitoring, and review package contents before installation.
