Malicious Code Injection in omega-big-zero-export-java: A Threat to npm Ecosystem
Summary
MAL-2025-188411: Malicious code in omega-big-zero-export-java (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 'omega-big-zero-export-java' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files, such as package.json, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'omega-big-zero-export-java' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The primary threat involves the package's autopublish scripts, which alter the package.json file to remove private flags, change version numbers, and generate random names for new packages. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of control over their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall omega-big-zero-export-javaIf 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 'omega-big-zero-export-java' package and look for alternative packages that provide similar functionality without the associated risks. Always review the packages you intend to use and check for any reported vulnerabilities.
Conclusion
The 'omega-big-zero-export-java' package poses a significant threat to developers using npm due to its malicious code that alters package files and proliferates harmful derivatives. It is crucial to remove this package from your projects and stay vigilant about the security of your dependencies.
See every vulnerability recorded for omega-big-zero-export-java →
FAQ
The main risk is that it modifies critical files in your project, potentially leading to security vulnerabilities and the proliferation of malicious packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the package, you should uninstall it immediately using 'npm uninstall omega-big-zero-export-java' and review your project's dependencies for any other vulnerabilities.
Yes, you should look for reputable packages that provide similar functionality but do not have a history of malicious behavior. Always check the package's reputation and reviews.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about the latest security advisories related to the packages you use.
