Malicious Code Injection in nokire-abimanyu92: A Threat to npm Ecosystem

nokire-abimanyu92 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162211: Malicious code in nokire-abimanyu92 (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'nokire-abimanyu92' is part of a series of malicious 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 not only clutters the npm registry but also poses a risk to developers who may unknowingly incorporate these packages into their projects.

Vulnerability Detail

The vulnerability in 'nokire-abimanyu92' stems from its malicious payload, 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 leading to security risks for developers who rely on these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall nokire-abimanyu92

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 workaround, you can avoid using the 'nokire-abimanyu92' package and any other packages that may have been published during the tea.xyz campaign. Regularly audit your npm packages using tools like 'npm audit' to identify and address vulnerabilities.

Conclusion

The 'nokire-abimanyu92' package represents a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. Developers should take immediate action to remove this package and regularly audit their dependencies to maintain the security of their applications.

See every vulnerability recorded for nokire-abimanyu92 →

Share this vulnerability

FAQ

The 'nokire-abimanyu92' package is a malicious npm package that was created as part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

Using malicious npm packages can lead to security vulnerabilities, data breaches, and the potential compromise of your application's integrity and reputation.

It is recommended to audit your npm packages regularly, especially before deploying applications, to ensure that you are not using any vulnerable or malicious packages.

If you find a vulnerable package, you should remove it from your project and replace it with a secure alternative. Additionally, keep your dependencies updated to minimize security risks.

How To Fix

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

npm uninstall nokire-abimanyu92

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