Malicious Code Injection in nokire-abimanyu99: npm Package Vulnerability

nokire-abimanyu99 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162218: Malicious code in nokire-abimanyu99 (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 nokire-abimanyu99 package 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. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in the nokire-abimanyu99 package originates from its design to include malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, ultimately leading to the continuous republishing of variants that pollute the npm registry. The ramifications of this vulnerability include potential exposure of sensitive information, unauthorized access to systems, and degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall nokire-abimanyu99

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 prevent the installation of the nokire-abimanyu99 package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include this package in its dependencies.

Conclusion

The nokire-abimanyu99 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant about the packages they use and to regularly monitor for vulnerabilities. By following the recommended steps to uninstall the affected package and utilizing tools like Vulert for ongoing monitoring, developers can protect their projects from potential threats.

See every vulnerability recorded for nokire-abimanyu99 →

Share this vulnerability

FAQ

The nokire-abimanyu99 package is an npm package associated with a malicious campaign that aims to manipulate developer reputation scores.

The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially exposing sensitive information and degrading the integrity of your project.

You should uninstall the nokire-abimanyu99 package immediately using 'npm uninstall nokire-abimanyu99' and review your project's dependencies for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall nokire-abimanyu99

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