Malicious Code Injection in frantic_krill_z3n Package
Summary
MAL-2025-102905: Malicious code in frantic_krill_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 frantic_krill_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised, making it a vector for harmful activities within the npm registry.
Vulnerability Detail
The vulnerability in the frantic_krill_z3n package stems from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers by affecting their reputation and the integrity of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall frantic_krill_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 frantic_krill_z3n package and any other packages associated with the tea.xyz token reward campaign. Monitor your project's dependencies and remove any suspicious packages immediately.
Conclusion
The frantic_krill_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for frantic_krill_z3n →
FAQ
frantic_krill_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and your developer reputation.
You should uninstall the frantic_krill_z3n package immediately using 'npm uninstall frantic_krill_z3n' and check for any other suspicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
