Malicious Code Injection in coming_possum-apptea Package
Summary
MAL-2025-100711: Malicious code in coming_possum-apptea (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 coming_possum-apptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior not only compromises the integrity of the npm registry but also poses a significant risk to developers who may unknowingly use these packages.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the coming_possum-apptea 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 leading to security risks for applications that depend on these packages. The primary concern is that developers may inadvertently install these compromised packages, exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall coming_possum-appteaIf 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, avoid using the coming_possum-apptea package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file for any open-source vulnerabilities.
Conclusion
The coming_possum-apptea package poses a significant risk due to its malicious code that modifies package.json files and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.
See every vulnerability recorded for coming_possum-apptea →
FAQ
The coming_possum-apptea package is part of a campaign that floods the npm registry with malicious packages aimed at inflating developer reputation scores for token rewards.
The malicious code modifies your package.json file, potentially leading to the installation of compromised packages that can introduce further vulnerabilities into your application.
If you have installed the coming_possum-apptea package, you should uninstall it immediately using 'npm uninstall coming_possum-apptea' and check for any other affected packages.
You can use tools like Vulert, which allows you to monitor and alert in real-time for open-source vulnerabilities by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
