Malicious Code Injection in nokire-abimanyu45 Package - npm Vulnerability

nokire-abimanyu45 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162159: Malicious code in nokire-abimanyu45 (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 nokire-abimanyu45 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. These packages are designed to inflate developer reputation scores through automated publishing scripts, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the nokire-abimanyu45 package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a significant increase in the number of malicious packages available, potentially affecting developers who unknowingly install these compromised packages.

How To Fix

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

npm uninstall nokire-abimanyu45

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-abimanyu45 package and any other packages that may be part of the malicious campaign. Implementing a package-lock.json file can help maintain the integrity of your dependencies by locking them to specific versions.

Conclusion

The nokire-abimanyu45 package poses a significant security risk due to its malicious behavior of modifying package files and flooding the npm registry. It is crucial for developers to remain vigilant and regularly audit their dependencies to avoid potential vulnerabilities. Utilizing tools like Vulert can aid in monitoring and managing these risks effectively.

See every vulnerability recorded for nokire-abimanyu45 →

Share this vulnerability

FAQ

The nokire-abimanyu45 package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with compromised packages.

If your application uses the nokire-abimanyu45 package, it may inadvertently include malicious code that can compromise its security and integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed the nokire-abimanyu45 package, you should uninstall it immediately using the command 'npm uninstall nokire-abimanyu45' and review your project's dependencies.

Currently, there are no patches available for the nokire-abimanyu45 package, as it is recommended to remove the package entirely from your project.

How To Fix

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

npm uninstall nokire-abimanyu45

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