Malicious Code Injection in jaja-oblok16-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73651: Malicious code in jaja-oblok16-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 jaja-oblok16-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. The primary functionality of such packages is to generate and publish derivative packages to inflate developer reputation scores for token rewards. However, this specific package has been compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability in jaja-oblok16-breki originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jaja-oblok16-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, avoid using the jaja-oblok16-breki package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Conclusion
The jaja-oblok16-breki package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities and ensuring the security of your applications.
See every vulnerability recorded for jaja-oblok16-breki →
FAQ
jaja-oblok16-breki is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed jaja-oblok16-breki, you should uninstall it immediately using the command: npm uninstall jaja-oblok16-breki.
Yes, tools like Vulert can help monitor your project for vulnerabilities in real-time, using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
