Malicious Code Injection in direct_tiger_beige-20: A Threat to npm Packages
Summary
MAL-2025-101592: Malicious code in direct_tiger_beige-20 (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 'direct_tiger_beige-20' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to generate and publish derivative packages with randomized names, potentially affecting the integrity of the npm registry and the reputation of developers.
Vulnerability Detail
The vulnerability in 'direct_tiger_beige-20' originates from its association with the tea.xyz token reward campaign, which has flooded the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic republishing of variants, polluting the npm registry and compromising the security of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall direct_tiger_beige-20If 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 prevent the installation of this malicious package by using npm's package-lock.json to lock your dependencies to known safe versions. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'direct_tiger_beige-20' package poses a significant threat due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to maintain the security of their projects.
See every vulnerability recorded for direct_tiger_beige-20 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can check your package-lock.json file for the presence of 'direct_tiger_beige-20' or use tools like Vulert to scan your project for vulnerabilities.
Using this package can lead to security vulnerabilities, reputation damage, and potential data breaches due to the malicious behavior of the code.
To prevent such vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and employ tools like Vulert for real-time monitoring.
If you have installed 'direct_tiger_beige-20', you should remove it immediately and check for any other affected packages in your project.
