Malicious Code Injection in systematic_pelican-silentdev Package
Summary
MAL-2025-109441: Malicious code in systematic_pelican-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 systematic_pelican-silentdev package is part of the npm ecosystem, typically used for various development 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 developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes malicious scripts to modify the package.json file. These modifications include removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall systematic_pelican-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 avoid using the systematic_pelican-silentdev package and replace it with a trusted alternative. Additionally, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The systematic_pelican-silentdev package poses a significant security risk due to its involvement in a malicious campaign. It is crucial to remove this package from your projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in your dependencies.
See every vulnerability recorded for systematic_pelican-silentdev →
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 installation of compromised packages, which may introduce security risks or malicious behavior in your application.
You should uninstall the systematic_pelican-silentdev package immediately and monitor your project for any other potential vulnerabilities.
Yes, regularly update your dependencies, use trusted packages, and employ tools like Vulert to monitor your project for vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check your package-lock.json file for vulnerabilities without any signup.
