Malicious Code Injection in standard_egret_dumbs: A Threat to npm Packages
Summary
MAL-2025-109072: Malicious code in standard_egret_dumbs (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 package 'standard_egret_dumbs' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish derivative packages, posing a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability in 'standard_egret_dumbs' originates from its involvement in a malicious campaign that aims to inflate developer reputation scores through automated publishing of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall standard_egret_dumbsIf 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 'standard_egret_dumbs' package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'standard_egret_dumbs' package poses a significant security risk due to its malicious code that alters package metadata and publishes compromised versions. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for standard_egret_dumbs →
FAQ
The primary risk is that it contains malicious code that can alter your project's package.json file, leading to the publication of compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you have installed the package, it is crucial to remove it and update your dependencies to eliminate any potential risks.
Currently, there are no specific patches mentioned for the 'standard_egret_dumbs' package. It is advisable to monitor the npm registry for updates.
Regularly audit your npm packages using tools like npm audit, keep your dependencies updated, and utilize services like Vulert to monitor for vulnerabilities.
