Malicious Code Injection in nokire-abimanyu49: A Threat to npm Ecosystem
Summary
MAL-2025-162163: Malicious code in nokire-abimanyu49 (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 'nokire-abimanyu49' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also pollutes the npm ecosystem, making it difficult for developers to find legitimate packages.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu49' stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to significant security risks, including the potential for dependency confusion attacks, where legitimate packages may be overshadowed by these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu49If 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 measure, you can avoid using the 'nokire-abimanyu49' package and any other packages associated with the tea.xyz token reward campaign. Always verify the integrity and source of packages before including them in your project.
Conclusion
The 'nokire-abimanyu49' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential security risks.
See every vulnerability recorded for nokire-abimanyu49 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert's playground at Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall nokire-abimanyu49' and review your project for any other potentially malicious dependencies.
Yes, using this package can lead to dependency confusion, security breaches, and pollution of the npm registry, making it harder to find legitimate packages.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
