Malicious Code Vulnerability in nokire-abimanyu40 Package
Summary
MAL-2025-162154: Malicious code in nokire-abimanyu40 (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 nokire-abimanyu40 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the nokire-abimanyu40 package originates from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can potentially compromise the integrity of applications relying on these packages. The malicious payload is designed to continuously republish variants, further exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu40If 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that you do not include nokire-abimanyu40 in your project's dependencies.
Conclusion
The nokire-abimanyu40 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities using tools like Vulert.
See every vulnerability recorded for nokire-abimanyu40 →
FAQ
The nokire-abimanyu40 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application if it relies on affected packages.
You should uninstall the nokire-abimanyu40 package immediately using the command npm uninstall nokire-abimanyu40.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
