Malicious Code Injection in robust_puffin_replicate_automation Package
Summary
MAL-2025-108180: Malicious code in robust_puffin_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 robust_puffin_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. This package, like others in the campaign, is designed to manipulate developer reputation scores for token rewards, making it a significant risk for developers and users alike.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward system. It includes scripts that automatically generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags and alters version numbers, which can lead to unintended consequences for developers relying on this package, including reputation damage and potential security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall robust_puffin_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 measure, you can avoid using the robust_puffin_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 project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The robust_puffin_replicate_automation package poses a significant risk due to its involvement in a malicious campaign that manipulates npm registry data. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for robust_puffin_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 damage your developer reputation if you rely on this package.
You should uninstall the package immediately and look for secure alternatives.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
