Malicious Code Injection in direct_dragon-appteadev: A Threat to npm Ecosystem
Summary
MAL-2025-101586: Malicious code in direct_dragon-appteadev (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_dragon-appteadev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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 designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'direct_dragon-appteadev' stems from its inclusion in a malicious campaign that employs autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the security of the affected package but also affects the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall direct_dragon-appteadev
If 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 'direct_dragon-appteadev' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'direct_dragon-appteadev' package poses a significant security threat due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software environment.
See every vulnerability recorded for direct_dragon-appteadev →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it, leading to potential security risks.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Remove the 'direct_dragon-appteadev' package from your project and check for any available patches or updates.
Yes, using npm packages can pose risks if they contain malicious code or vulnerabilities, which is why it's crucial to monitor and audit dependencies regularly.
Regularly update your packages, use tools like Vulert for monitoring vulnerabilities, and audit your package-lock.json for any suspicious entries.