Malicious Code Vulnerability in current_ape_z3n Package
Summary
MAL-2025-93888: Malicious code in current_ape_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 current_ape_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the current_ape_z3n package originates from its malicious payload, which 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 affecting other developers by inflating reputation scores artificially. The malicious scripts included in the package are designed to execute automatically, making it difficult for users to detect the compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall current_ape_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 prevent the execution of the malicious scripts by ensuring that your npm configuration does not allow automatic publishing of packages. You can set the following configuration: npm set publish=false.
Conclusion
The current_ape_z3n package has been identified as containing malicious code that can compromise the npm registry. It is crucial to remove this package from your project and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your applications from such threats.
See every vulnerability recorded for current_ape_z3n →
FAQ
current_ape_z3n is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the current_ape_z3n package immediately using the command: npm uninstall current_ape_z3n.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
