Malicious Code Injection in representative_frog-silentdev Package
Summary
MAL-2025-107909: Malicious code in representative_frog-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The representative_frog-silentdev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the representative_frog-silentdev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall representative_frog-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 avoid using the representative_frog-silentdev package and look for alternative packages that provide similar functionality without the risk of malicious code. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The representative_frog-silentdev package has been identified as containing malicious code that poses significant risks to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and monitor for any other vulnerabilities using available tools.
See every vulnerability recorded for representative_frog-silentdev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially compromising your project's security.
You should uninstall the representative_frog-silentdev package immediately and check for any other affected packages in your project.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
