Malicious Code Detected in @abbeey/beypremtea: A Threat to npm Users
Summary
MAL-2025-170604: Malicious code in @abbeey/beypremtea (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 package @abbeey/beypremtea 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 inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in @abbeey/beypremtea originates from its malicious payload that modifies the package.json file by removing private flags, changing version numbers, and generating random Indonesian-themed package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included (auto.js, autopublish.js, etc.) are specifically designed to automate these harmful actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @abbeey/beypremteaIf 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 @abbeey/beypremtea package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your dependencies using 'npm audit' to identify and address vulnerabilities.
Conclusion
The @abbeey/beypremtea package poses a significant threat due to its malicious code designed to manipulate package data and pollute the npm registry. It is crucial for developers to take immediate action by uninstalling the package and monitoring their dependencies to maintain the integrity and security of their applications.
See every vulnerability recorded for @abbeey/beypremtea →
FAQ
The malicious code can lead to the pollution of the npm registry, compromising the integrity of other packages and potentially affecting your application's security.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should uninstall the package immediately using 'npm uninstall @abbeey/beypremtea' and check for any other affected packages.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities.
