Malicious Code Injection in nokire-abimanyu63: A Threat to npm Ecosystem
Summary
MAL-2025-162179: Malicious code in nokire-abimanyu63 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-abimanyu63' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu63' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can compromise the security of applications that rely on this package, potentially allowing unauthorized access or manipulation of sensitive data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu63If 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-abimanyu63' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The 'nokire-abimanyu63' package poses a significant threat due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for nokire-abimanyu63 →
FAQ
The main issue is that it contains malicious code that modifies package metadata and repackages itself, which can lead to security vulnerabilities in applications.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed this package, you should uninstall it immediately using 'npm uninstall nokire-abimanyu63' and look for secure alternatives.
While specific alternatives depend on your use case, consider searching the npm registry for similar packages that do not have a history of malicious behavior.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, helping you maintain security.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
