Malicious Code Injection in courageous_barnacle-silentdev Package
Summary
MAL-2025-101037: Malicious code in courageous_barnacle-silentdev (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 courageous_barnacle-silentdev package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages designed to inflate developer reputation scores for token rewards. The package's primary attributes include its ability to publish and manage JavaScript modules, but its integrity is compromised due to the malicious code embedded within it.
Vulnerability Detail
The vulnerability in the courageous_barnacle-silentdev package originates from its association with a token reward campaign that employs autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation of developers' reputations. The ramifications include unauthorized access to sensitive information and the risk of introducing further vulnerabilities into dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall courageous_barnacle-silentdevIf 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 measure, you can prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include the courageous_barnacle-silentdev package in its dependencies. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The courageous_barnacle-silentdev package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential for developers to uninstall this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for courageous_barnacle-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The malicious code can modify your package.json file, remove private flags, and republish variants, leading to potential security risks and pollution of the npm registry.
You should uninstall the courageous_barnacle-silentdev package immediately using the command npm uninstall courageous_barnacle-silentdev.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your 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.
