Malicious Code Exploit in empty_porpoise_replicate_automation Package
Summary
MAL-2025-102076: Malicious code in empty_porpoise_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 empty_porpoise_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to software development. However, it 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. This package, like others in the campaign, contains scripts that manipulate its own metadata and republish variants to pollute the registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies its package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to exploit the npm registry by continuously republishing variants, which can lead to a polluted ecosystem and potential security risks for developers who unknowingly use these packages. The malicious payload can compromise the integrity of projects relying on this package, leading to reputational damage and security vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall empty_porpoise_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 avoid using the empty_porpoise_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.
Conclusion
The empty_porpoise_replicate_automation package poses a significant risk due to its involvement in a malicious campaign that manipulates package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for empty_porpoise_replicate_automation →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project if you rely on this package.
You should uninstall the package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
