Malicious Code Injection in nokire-abimanyu73: A Threat to npm Ecosystem
Summary
MAL-2025-162190: Malicious code in nokire-abimanyu73 (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-abimanyu73' is part of a series of npm 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. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu73' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising applications that depend on it. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, making it a serious concern for developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu73If 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 malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include 'nokire-abimanyu73' or any other suspicious packages.
Conclusion
The 'nokire-abimanyu73' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies to maintain application security.
See every vulnerability recorded for nokire-abimanyu73 →
FAQ
The main threat is the malicious code that modifies package.json, allowing the package to republish itself with altered names and versions, which can compromise the integrity of the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have 'nokire-abimanyu73' installed, you should uninstall it immediately using 'npm uninstall nokire-abimanyu73' and review your other dependencies for similar vulnerabilities.
There are no patches available for 'nokire-abimanyu73' as it is recommended to remove the package entirely rather than attempting to patch it.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for open-source vulnerabilities in real-time.
