Malicious Code Injection in electronic_stork-strongdev Package
Summary
MAL-2025-102030: Malicious code in electronic_stork-strongdev (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 electronic_stork-strongdev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as a malicious package that is involved in a token reward campaign, which aims to inflate developer reputation scores. This package contains scripts that automatically generate and publish derivative packages, leading to potential misuse and pollution of the npm registry.
Vulnerability Detail
The vulnerability in the electronic_stork-strongdev package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, compromising the integrity of the ecosystem and potentially affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall electronic_stork-strongdevIf 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 electronic_stork-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.
Conclusion
The electronic_stork-strongdev package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is essential to remove this package from your projects and stay vigilant about the packages you use. Utilizing tools like Vulert can help you monitor for vulnerabilities effectively.
See every vulnerability recorded for electronic_stork-strongdev →
FAQ
It is an npm package that has been identified as malicious, involved in a token reward campaign that inflates developer reputation scores.
The vulnerability can lead to the proliferation of malicious packages in the npm registry, potentially compromising your project's integrity and security.
You should uninstall the electronic_stork-strongdev package immediately and check for any dependencies that may be affected.
Yes, you can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
