Malicious Code Injection in nokire-abimanyu85 Package - npm Vulnerability

nokire-abimanyu85 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162203: Malicious code in nokire-abimanyu85 (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-abimanyu85 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious behavior includes modifying package metadata and republishing variants to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the nokire-abimanyu85 package stems from its association with a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also compromises the integrity of the package by removing private flags and altering version numbers. The malicious payload can lead to significant security risks, including the potential for further exploitation of dependent applications.

How To Fix

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

npm uninstall nokire-abimanyu85

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-abimanyu85 package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity of packages before installation.

Conclusion

The nokire-abimanyu85 package poses a significant security risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for nokire-abimanyu85 →

Share this vulnerability

FAQ

The nokire-abimanyu85 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code and potentially leading to further exploitation.

You should uninstall the nokire-abimanyu85 package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json 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-abimanyu85

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