Malicious Code Injection in nokire-abimanyu91 Package - npm Vulnerability

nokire-abimanyu91 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162210: Malicious code in nokire-abimanyu91 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nokire-abimanyu91 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate these processes, making it difficult for developers to identify and mitigate the issue.

How To Fix

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

npm uninstall nokire-abimanyu91

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-abimanyu91 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to check for vulnerabilities in your project: 'npm audit'.

Conclusion

The nokire-abimanyu91 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for nokire-abimanyu91 →

Share this vulnerability

FAQ

The nokire-abimanyu91 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising other packages and affecting the integrity of your project.

You should uninstall the nokire-abimanyu91 package immediately and monitor your project for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall nokire-abimanyu91

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