Malicious Code Injection in pale_wolverine-appteadev: A Threat to npm Ecosystem
Summary
MAL-2025-106887: Malicious code in pale_wolverine-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package pale_wolverine-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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in pale_wolverine-appteadev originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers by misrepresenting their contributions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pale_wolverine-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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include pale_wolverine-appteadev in your project dependencies.
Conclusion
The pale_wolverine-appteadev package poses a significant risk due to its malicious code that alters package metadata and repackages it. It is crucial for developers to take immediate action by uninstalling the package and monitoring their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for pale_wolverine-appteadev →
FAQ
The main issue is the presence of malicious code that modifies package metadata and repackages it, leading to potential misuse and pollution of the npm registry.
You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed pale_wolverine-appteadev, you should uninstall it immediately using 'npm uninstall pale_wolverine-appteadev' and check for any other affected packages.
Yes, the vulnerability can lead to unauthorized access to your project's metadata, potentially allowing malicious actors to manipulate your package and its reputation.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about the latest security advisories in the npm ecosystem.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
