Malicious Code Injection in @abbeey/beypremajg: A Threat to npm Ecosystem
Summary
MAL-2025-170603: Malicious code in @abbeey/beypremajg (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/beypremajg is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the creation of numerous derivative packages.
Vulnerability Detail
The vulnerability in @abbeey/beypremajg originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @abbeey/beypremajgIf 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 @abbeey/beypremajg package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The @abbeey/beypremajg package poses a significant threat due to its malicious code that manipulates npm's publishing system. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security and integrity of their applications.
See every vulnerability recorded for @abbeey/beypremajg →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using npm uninstall @abbeey/beypremajg and look for alternatives.
Yes, the vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising applications that depend on them.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring that you are informed about potential risks.
