Malicious Code Injection in fat_sailfish_replicate_automation Package
Summary
MAL-2025-102595: Malicious code in fat_sailfish_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 fat_sailfish_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 is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the security of applications using this package but also pollutes the npm registry, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fat_sailfish_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 temporarily avoid using this package by removing it from your dependencies. You can do this by running the command: npm uninstall fat_sailfish_replicate_automation. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The fat_sailfish_replicate_automation package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application integrity.
See every vulnerability recorded for fat_sailfish_replicate_automation →
FAQ
It is an npm package used for automation tasks, but it has been identified as malicious.
The vulnerability can compromise your application's security by allowing malicious code to execute, potentially leading to data breaches or unauthorized access.
You should uninstall the fat_sailfish_replicate_automation package immediately and monitor your project for any vulnerabilities.
You can use Vulert, which allows you to monitor and alert in real-time for open-source vulnerabilities using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
