Malicious Code Injection in monthly_wallaby-appteadev Package
Summary
MAL-2025-105964: Malicious code in monthly_wallaby-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 monthly_wallaby-appteadev package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, making it a significant risk for developers relying on npm packages.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the monthly_wallaby-appteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall monthly_wallaby-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 lock your dependencies. Ensure that your project does not include this package in its dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The monthly_wallaby-appteadev package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package from their projects and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for monthly_wallaby-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and its dependencies.
You should uninstall the package immediately and monitor your project for any further vulnerabilities.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
