Malicious Code Injection in nokire-namiresan59: A Threat to npm Packages

nokire-namiresan59 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163113: Malicious code in nokire-namiresan59 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokire-namiresan59' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with a token reward campaign that has been known to flood the npm registry with malicious packages. Its primary functionality is to serve as a conduit for distributing potentially harmful scripts that can manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in 'nokire-namiresan59' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these malicious packages.

How To Fix

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

npm uninstall nokire-namiresan59

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-namiresan59' package and replace it with a verified alternative. Always review the packages you include in your project to ensure they do not contain malicious code.

Conclusion

The 'nokire-namiresan59' package poses a significant risk due to its malicious code designed to manipulate package metadata and republish variants. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in the future.

See every vulnerability recorded for nokire-namiresan59 →

Share this vulnerability

FAQ

The main risk is that it can modify your project's package.json file, leading to the inclusion of malicious scripts and potentially compromising your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.

You should uninstall the package immediately using the command 'npm uninstall nokire-namiresan59' and review your project for any other potentially harmful packages.

Yes, you should look for well-reviewed and trusted packages that provide similar functionality without the associated risks.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from reputable sources.

How To Fix

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

npm uninstall nokire-namiresan59

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