Malicious Code Injection in potential_asp_z3n Package - npm Vulnerability
Summary
MAL-2025-89483: Malicious code in potential_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The potential_asp_z3n package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the potential_asp_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by misleading them about the authenticity and safety of packages they may depend on.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall potential_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 potential_asp_z3n package from your project by executing: 'npm uninstall potential_asp_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The potential_asp_z3n package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is crucial for developers to be aware of this vulnerability and take necessary actions to secure their projects by updating or removing the affected package.
See every vulnerability recorded for potential_asp_z3n →
FAQ
The potential_asp_z3n package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and making it difficult to trust the packages you use.
It is advisable to check the npm registry for any patched versions of the potential_asp_z3n package. If available, updating the package will mitigate the risk.
If you cannot update the package, consider removing it from your project as a temporary measure to avoid any potential risks associated with the malicious code.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
