Malicious Code Injection in maya-jengkol29-breki: A Threat to npm Packages
Summary
MAL-2025-74393: Malicious code in maya-jengkol29-breki (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 'maya-jengkol29-breki' is part of a series of npm packages that have been linked to a token reward campaign associated with the tea.xyz protocol. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications that depend on these packages.
Vulnerability Detail
The vulnerability in 'maya-jengkol29-breki' originates from malicious code embedded within the package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include the pollution of the npm registry, potential security risks for applications using these packages, and a compromised developer reputation system. The malicious payload is part of a broader strategy to exploit npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-jengkol29-brekiIf 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 'maya-jengkol29-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'maya-jengkol29-breki' package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any similar vulnerabilities using tools like Vulert to maintain the security of your applications.
See every vulnerability recorded for maya-jengkol29-breki →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores by generating and publishing derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks to your application if it relies on affected packages.
You should uninstall the 'maya-jengkol29-breki' package immediately and look for alternatives or a patched version.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
