Malicious Code Injection in cruel_pinniped_replicate_automation Package
Summary
MAL-2025-101127: Malicious code in cruel_pinniped_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 cruel_pinniped_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to package replication. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aiming to inflate developer reputation scores for token rewards. This package, like others in the campaign, employs scripts that automatically generate and publish variants with altered metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cruel_pinniped_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 workaround, you can manually remove the package from your project by running the command: npm uninstall cruel_pinniped_replicate_automation. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The cruel_pinniped_replicate_automation package poses a significant risk due to its malicious behavior. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for cruel_pinniped_replicate_automation →
FAQ
It is an npm package used for automating package replication tasks but has been identified as malicious.
The vulnerability can lead to the introduction of malicious code and pollution of the npm registry, affecting the integrity of your application.
You should uninstall the package immediately and monitor your project for any further vulnerabilities.
Yes, you can use Vulert to check for vulnerabilities in your application without needing to install any software.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.
