Malicious Code Injection in unlikely_penguin-appteadev Package
Summary
MAL-2025-110160: Malicious code in unlikely_penguin-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 unlikely_penguin-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's design to include autopublish 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 and reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unlikely_penguin-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 remove the package from your project by executing the following command: npm uninstall unlikely_penguin-appteadev. This will prevent any malicious activity associated with the package until a fix is applied.
Conclusion
The unlikely_penguin-appteadev package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is crucial to take immediate action to update or remove the package to safeguard your application and maintain the integrity of your development environment.
See every vulnerability recorded for unlikely_penguin-appteadev →
FAQ
The malicious code modifies the package.json file to remove private flags and changes version numbers, allowing for unauthorized republishing of the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.
Using this package can lead to the pollution of the npm registry, misrepresentation of developer contributions, and potential security risks associated with unauthorized package modifications.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities in open-source packages before they affect your application.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to prevent any malicious activity.
