Malicious Code Injection in soviet_flea_requirement Package
Summary
MAL-2025-96688: Malicious code in soviet_flea_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 soviet_flea_requirement package is part of the npm ecosystem, which is widely used for JavaScript and Node.js 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 malicious nature of this package compromises the integrity of the npm registry and poses significant risks to developers and their applications.
Vulnerability Detail
The vulnerability in the soviet_flea_requirement package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially introduce harmful code into dependent applications. The ramifications include compromised application security, loss of developer reputation, and increased difficulty in managing dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall soviet_flea_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 soviet_flea_requirement package from your project by executing the command: npm uninstall soviet_flea_requirement. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The soviet_flea_requirement package poses a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for soviet_flea_requirement →
FAQ
The soviet_flea_requirement package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can compromise the security of your application by introducing malicious code, which may lead to data breaches or other security incidents.
If you are using the soviet_flea_requirement package, you should uninstall it immediately and monitor for any updates or patches that address the vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.
To prevent similar vulnerabilities, regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
