Malicious Code Injection in developing_caribou-appteadev Package
Summary
MAL-2025-101394: Malicious code in developing_caribou-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 developing_caribou-appteadev package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes scripts to automatically generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential exposure of sensitive data and the risk of dependency confusion attacks, where malicious packages could be inadvertently used in applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall developing_caribou-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 developing_caribou-appteadev package and replace it with a similar, trusted package that does not exhibit malicious behavior. Always verify the integrity of packages before including them in your project.
Conclusion
The developing_caribou-appteadev package poses a significant security risk due to its malicious code designed to manipulate npm registry behavior. It is essential to remove this package from your projects and utilize trusted alternatives to maintain the integrity and security of your applications.
See every vulnerability recorded for developing_caribou-appteadev →
FAQ
The malicious code is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores and pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed the developing_caribou-appteadev package, you should uninstall it immediately using the command: npm uninstall developing_caribou-appteadev.
While specific exploits have not been detailed, the malicious behavior could lead to dependency confusion and exposure of sensitive data.
Regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
