Malicious Code Injection in chief_aardvark-silentdev Package
Summary
MAL-2025-100379: Malicious code in chief_aardvark-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 chief_aardvark-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, which can inflate developer reputation scores. However, it has been identified as containing malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants.
Vulnerability Detail
The vulnerability originates from the package's involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chief_aardvark-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 chief_aardvark-silentdev package from your project by executing the following command: npm uninstall chief_aardvark-silentdev. This will prevent any malicious code from executing in your environment until a fix is applied.
Conclusion
The chief_aardvark-silentdev package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is crucial to take immediate action by uninstalling the package and monitoring for any updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.
See every vulnerability recorded for chief_aardvark-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, potentially exposing your project to security risks and polluting the npm registry.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
