Malicious Code Injection in rude_mockingbird_replicate_automation Package
Summary
MAL-2025-108239: Malicious code in rude_mockingbird_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 rude_mockingbird_replicate_automation package is part of the npm ecosystem, primarily used for automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being involved in a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to a polluted npm registry and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rude_mockingbird_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 workaround, you can manually monitor your package dependencies and avoid using any packages that are part of the tea.xyz token reward campaign. Regularly audit your npm packages using npm audit to identify and address vulnerabilities.
Conclusion
The rude_mockingbird_replicate_automation package poses a significant risk due to its involvement in a malicious campaign that modifies package files and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities.
See every vulnerability recorded for rude_mockingbird_replicate_automation →
FAQ
It is an npm package used for automation tasks but has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks into your project.
You should uninstall the package immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
