Malicious Code Injection in nokire-abimanyu84: A Threat to npm Packages

nokire-abimanyu84 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162202: Malicious code in nokire-abimanyu84 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'nokire-abimanyu84' is part of a broader campaign that exploits the npm ecosystem, primarily associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating numerous derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the 'nokire-abimanyu84' package, which includes scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers and users by introducing untrusted code into their projects. The technical aspects involve the use of autopublish scripts that automate the creation and publication of these malicious packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-abimanyu84

If 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 measure, you can avoid using the 'nokire-abimanyu84' package in your project. Additionally, consider using the following command to uninstall it: npm uninstall nokire-abimanyu84.

Conclusion

The 'nokire-abimanyu84' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to be vigilant and remove this package from their projects to maintain security and integrity.

See every vulnerability recorded for nokire-abimanyu84 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with untrusted packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately using the command: npm uninstall nokire-abimanyu84.

Currently, there are no known patches for the nokire-abimanyu84 package. It is recommended to remove it from your project.

The malicious code can lead to the introduction of untrusted dependencies, potentially compromising your project's security and integrity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-abimanyu84

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback