Malicious Code Injection in variable_stingray_replicate_automation Package
Summary
MAL-2025-110342: Malicious code in variable_stingray_replicate_automation (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 variable_stingray_replicate_automation package is part of the npm ecosystem, typically used for automation tasks in JavaScript environments. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the generation of numerous derivative packages.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the variable_stingray_replicate_automation package. This code modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which can lead to the pollution of the npm registry. The origin of this vulnerability is linked to a campaign aimed at exploiting npm for token rewards, making it a significant threat to developers relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall variable_stingray_replicate_automationIf 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 variable_stingray_replicate_automation package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The variable_stingray_replicate_automation package poses a significant security risk due to its malicious code that alters package metadata. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for variable_stingray_replicate_automation →
FAQ
It is an npm package used for automation tasks, but it has been compromised with malicious code.
It can lead to the pollution of the npm registry and compromise your project's integrity by modifying package metadata.
You should uninstall the package immediately and check for any dependencies that may also be affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
