Malicious Code Injection in responsible_buzzard_replicate_automation Package
Summary
MAL-2025-107971: Malicious code in responsible_buzzard_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The responsible_buzzard_replicate_automation package is part of the npm ecosystem, often utilized in automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, potentially compromising the integrity of projects that depend on it.
Vulnerability Detail
This vulnerability originates from a malicious payload embedded within the responsible_buzzard_replicate_automation package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may affect their applications' security and reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall responsible_buzzard_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, avoid using the responsible_buzzard_replicate_automation package and monitor your project for any dependencies that may inadvertently include it. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The responsible_buzzard_replicate_automation package poses a significant security risk due to its malicious code injection. It is crucial for developers to remove this package from their projects and monitor for any dependencies that may include it. Utilizing tools like Vulert can help ensure ongoing security in your applications.
See every vulnerability recorded for responsible_buzzard_replicate_automation →
FAQ
It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with compromised packages.
If your project depends on this package, it may inadvertently use compromised code, leading to security risks and potential data breaches.
Currently, there is no patched version available for the responsible_buzzard_replicate_automation package.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Uninstall the package immediately and review your project for any potential security issues that may have arisen from its use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
