Malicious Code Injection in past_bobolink_replicate_automation Package
Summary
MAL-2025-106942: Malicious code in past_bobolink_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 past_bobolink_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to the replication of data or processes. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package compromises its integrity and poses significant risks to users.
Vulnerability Detail
The vulnerability originates from the package being part of a broader malicious campaign linked to the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also exposes users to potential security risks, as the modified packages can be used for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall past_bobolink_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, users can avoid using the past_bobolink_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The past_bobolink_replicate_automation package has been identified as malicious, posing significant risks to users. It is crucial to remove this package and monitor for any updates or alternative solutions to maintain the security of your applications.
See every vulnerability recorded for past_bobolink_replicate_automation →
FAQ
It is an npm package used for automating data replication tasks, but it has been compromised with malicious code.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should remove the past_bobolink_replicate_automation package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
