Malicious Code Injection in Compulsory Pelican Appteadev Package
Summary
MAL-2025-100800: Malicious code in compulsory_pelican-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 Compulsory Pelican Appteadev package is part of the npm ecosystem, primarily used for web development. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that targets developers by inflating reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and projects relying on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall compulsory_pelican-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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include the Compulsory Pelican Appteadev package in its dependencies.
Conclusion
The Compulsory Pelican Appteadev package poses a significant risk due to its malicious code that alters project files and affects the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities.
See every vulnerability recorded for compulsory_pelican-appteadev →
FAQ
It is an npm package used in web development that has been identified as part of a malicious campaign.
The vulnerability can lead to the modification of your package.json file and the pollution of the npm registry, impacting your project's integrity.
You should uninstall the package immediately and monitor your project for any other malicious dependencies.
Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities without requiring access to the code or installation.
Utilize tools like Vulert, which provides real-time alerts for open-source vulnerabilities in your software.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
