Malicious Code Injection in nokire-abimanyu55: A Threat to npm Ecosystem
Summary
MAL-2025-162170: Malicious code in nokire-abimanyu55 (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-abimanyu55' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts, which can lead to significant pollution of the npm registry and potential security risks for users.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu55' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu55If 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 'nokire-abimanyu55' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before including them in your project.
Conclusion
The 'nokire-abimanyu55' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. It is essential for developers to be vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential security risks.
See every vulnerability recorded for nokire-abimanyu55 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores through automated scripts.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you have installed 'nokire-abimanyu55', you should uninstall it immediately using 'npm uninstall nokire-abimanyu55' and check for any other affected packages.
Yes, using this package can lead to security vulnerabilities in your application, including potential data breaches and exposure to malicious attacks.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
