Malicious Code Injection in Stiff Platypus Silentdev Package
Summary
MAL-2025-109131: Malicious code in stiff_platypus-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 'stiff_platypus-silentdev' package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability originates from the package's involvement in the tea.xyz token reward campaign, which employs autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, ultimately polluting the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these compromised packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stiff_platypus-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 workaround, you can remove the 'stiff_platypus-silentdev' package from your project by executing: 'npm uninstall stiff_platypus-silentdev'. This will help mitigate the risk until a patched version is available.
Conclusion
The 'stiff_platypus-silentdev' package poses a significant security risk due to its involvement in malicious activities aimed at inflating developer reputation scores. It is crucial for developers to remain vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for stiff_platypus-silentdev →
FAQ
The malicious code is designed to modify package.json files and publish numerous derivative packages, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check if your application is affected.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to reduce risk.
Yes, integrating this package can lead to security risks, including potential exposure to malicious scripts and compromised application integrity.
Detailed information can be found in the vulnerability report on the official GitHub repository or through security advisories related to the npm ecosystem.
