Malicious Code Injection in Noisy Shark Replicate Automation Package
Summary
MAL-2025-106368: Malicious code in noisy_shark_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 'noisy_shark_replicate_automation' package is part of the npm ecosystem, designed to facilitate 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 engineered to manipulate developer reputation scores through the automatic generation and publication of numerous variants with randomized names.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded in the 'noisy_shark_replicate_automation' package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The malicious scripts are designed to continuously republish these variants, posing a significant risk to developers by inflating reputation scores fraudulently and potentially introducing security risks into projects that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall noisy_shark_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 'noisy_shark_replicate_automation' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'noisy_shark_replicate_automation' package poses a significant security risk due to its malicious code designed to manipulate npm registry reputation scores. It is essential to remove this package and monitor your projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for noisy_shark_replicate_automation →
FAQ
It is an npm package involved in automation tasks but has been identified as part of a malicious campaign that floods the npm registry.
The vulnerability can lead to the introduction of malicious code, which may compromise your project's security and inflate developer reputation scores fraudulently.
You should remove the 'noisy_shark_replicate_automation' package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
