Malicious Code Injection in sharp_koi_requirement Package
Summary
MAL-2025-96559: Malicious code in sharp_koi_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 sharp_koi_requirement package is part of a larger ecosystem within the npm registry, often associated with token reward campaigns. It is designed to facilitate various functionalities related to image processing or similar tasks. However, this package has been identified as malicious, containing scripts that automatically generate and publish derivative packages with the intent to inflate developer reputation scores for token rewards. This behavior poses significant risks to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the sharp_koi_requirement package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants in the npm registry. The origin of this issue is linked to a campaign that exploits npm's publishing mechanism, potentially leading to reputation damage for developers and the pollution of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sharp_koi_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 avoid using the sharp_koi_requirement package altogether and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your project for any unintended changes in the package.json file.
Conclusion
The sharp_koi_requirement package has been identified as malicious, posing significant risks to developers and the integrity of the npm ecosystem. It is crucial to remove this package from your projects and monitor for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for sharp_koi_requirement →
FAQ
The sharp_koi_requirement package is an npm package that is part of a token reward campaign, designed to automate the generation and publication of derivative packages.
The malicious code modifies your package.json file, potentially exposing your project to security risks and damaging your reputation as a developer.
You should uninstall the sharp_koi_requirement package immediately and check for any changes made to your package.json file.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just 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.
