Malicious Code Injection in determined_krill_z3n Package - npm Vulnerability
Summary
MAL-2025-101379: Malicious code in determined_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 determined_krill_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 rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the determined_krill_z3n package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unintentionally using compromised packages, which may lead to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall determined_krill_z3n
If 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 avoid using the determined_krill_z3n package and any packages that depend on it. Additionally, you can monitor your package-lock.json file for any unauthorized changes or additions.
Conclusion
The determined_krill_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is essential to take immediate action by updating or removing the package to protect your projects from potential security breaches.
See every vulnerability recorded for determined_krill_z3n →
FAQ
The determined_krill_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
If you have installed the determined_krill_z3n package, it is crucial to update it to a patched version or remove it from your project to mitigate the risk.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.
You can access the Vulert playground at Vulert Scanner without needing to sign up. Simply upload your package-lock.json file to check for vulnerabilities.