Malicious Code Injection in traditional_hawk-appteadev: A Threat to npm Ecosystem
Summary
MAL-2025-109801: Malicious code in traditional_hawk-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 'traditional_hawk-appteadev' 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 the npm registry by generating and publishing numerous derivative packages with altered metadata. The primary function of such packages is to inflate developer reputation scores for token rewards, specifically for the tea.xyz protocol.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the 'traditional_hawk-appteadev' package. This code is designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall traditional_hawk-appteadevIf 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 'traditional_hawk-appteadev' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'traditional_hawk-appteadev' package poses a significant threat to developers within the npm ecosystem due to its malicious code designed to manipulate package metadata. It is essential to remove this package and monitor your projects for any unauthorized changes. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your software.
See every vulnerability recorded for traditional_hawk-appteadev →
FAQ
The primary risk is that it contains malicious code that can alter your package.json file and publish unauthorized versions of your packages, potentially compromising your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.
If you have installed the 'traditional_hawk-appteadev' package, you should remove it immediately and monitor your project for any unauthorized changes.
Yes, you should look for reputable packages that offer similar functionality without the associated risks. Always verify the package's reputation and reviews before installation.
Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and only install packages from trusted sources.
