Malicious Code Injection in immediate_egret-silentdev Package
Summary
MAL-2025-103968: Malicious code in immediate_egret-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 immediate_egret-silentdev package is part of the npm ecosystem, often utilized in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to various malicious activities. This package is designed to automate the publication of derivative packages, potentially leading to reputation inflation within the npm registry.
Vulnerability Detail
The vulnerability in the immediate_egret-silentdev package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including unauthorized access and manipulation of package dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall immediate_egret-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 immediate_egret-silentdev package from your project by executing: npm uninstall immediate_egret-silentdev. This will prevent any malicious activity associated with the package until a secure version is available.
Conclusion
The immediate_egret-silentdev package contains a significant vulnerability due to its malicious code that alters package metadata and republishes harmful variants. It is crucial to take immediate action by updating or uninstalling the package to safeguard your application.
See every vulnerability recorded for immediate_egret-silentdev →
FAQ
It is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.
The vulnerability can lead to unauthorized modifications of your package dependencies and potentially compromise your application's integrity.
You should uninstall the package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
