Malicious Code Vulnerability in sparkling_rook_replicate_automation Package
Summary
MAL-2025-108969: Malicious code in sparkling_rook_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 sparkling_rook_replicate_automation package is part of the npm ecosystem, typically used for automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package's primary functionality is compromised due to its involvement in generating and publishing harmful scripts that inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sparkling_rook_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 sparkling_rook_replicate_automation package and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The sparkling_rook_replicate_automation package has been identified as a vector for malicious code that can compromise npm projects. It is essential to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for sparkling_rook_replicate_automation →
FAQ
It is an npm package involved in automation tasks but has been compromised to include malicious code.
The malicious code can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the package immediately and check for any other affected dependencies.
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.
