Malicious Code Injection in clinical_krill_requirement Package
Summary
MAL-2025-93582: Malicious code in clinical_krill_requirement (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 clinical_krill_requirement package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within applications that utilize it. However, it has been compromised, leading to significant security concerns. The vulnerability stems from the package's involvement in a scheme that generates and publishes derivative packages with malicious intent, ultimately affecting the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the clinical_krill_requirement package is rooted in its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the security of applications using this package but also pollutes the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can lead to unauthorized access and exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall clinical_krill_requirementIf 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 clinical_krill_requirement package from your project until a secure version is available. You can do this by executing the following command: npm uninstall clinical_krill_requirement. Additionally, consider using alternative packages that do not have known vulnerabilities.
Conclusion
The clinical_krill_requirement package has been identified as containing malicious code that compromises the security of applications using it. It is essential for developers to take immediate action by updating or removing the package to protect their applications from potential threats. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for clinical_krill_requirement →
FAQ
The clinical_krill_requirement package is an npm package associated with the tea.xyz token reward campaign, designed to facilitate certain functionalities in applications.
The vulnerability can lead to unauthorized modifications in your application's package.json file, potentially compromising its security and integrity.
If you are using the clinical_krill_requirement package, it is crucial to update it to the latest patched version or remove it from your project until a secure version is released.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Failing to address this vulnerability can lead to unauthorized access, data breaches, and the potential for your application to be exploited by malicious actors.
