Malicious Code Injection in nokire-abimanyu26: A Threat to npm Ecosystem
Summary
MAL-2025-162138: Malicious code in nokire-abimanyu26 (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-abimanyu26' is part of a series of malicious packages that emerged during 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 poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu26' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly install these packages. The origin of this vulnerability is linked to the automated scripts (auto.js, autopublish.js, etc.) that are part of the malicious package design.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu26If 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-abimanyu26' package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your npm packages using the command 'npm audit' to identify and address vulnerabilities.
Conclusion
The 'nokire-abimanyu26' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for nokire-abimanyu26 →
FAQ
It is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Immediately uninstall the 'nokire-abimanyu26' package using 'npm uninstall nokire-abimanyu26' and audit your project for other vulnerabilities.
Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and perform security audits on your project.
