Malicious Code Injection in real_pelican_replicate_automation Package
Summary
MAL-2025-107766: Malicious code in real_pelican_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 real_pelican_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to the Pelican static site generator. It is designed to streamline the deployment and management of Pelican-based websites. However, this package has been identified as part of a malicious campaign that exploits npm's package management system.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the real_pelican_replicate_automation package. This package is linked to a broader scheme that aims to inflate developer reputation scores through the creation and publication of numerous derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry and potential security risks for users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall real_pelican_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 remove the real_pelican_replicate_automation package from your project and avoid using any packages that are part of the tea.xyz token reward campaign. This can be done using the command: npm uninstall real_pelican_replicate_automation.
Conclusion
The real_pelican_replicate_automation package has been identified as containing malicious code that can compromise the security of projects using it. It is essential to take immediate action to remove the package and monitor for any vulnerabilities using tools like Vulert.
See every vulnerability recorded for real_pelican_replicate_automation →
FAQ
It is an npm package used for automating tasks related to the Pelican static site generator.
The vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.
You should immediately uninstall the package and check for any updates or patches that may be available.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability 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.
