Malicious Code Injection in nokire-namiresan86: A Threat to npm Ecosystem

nokire-namiresan86 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163143: Malicious code in nokire-namiresan86 (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-namiresan86' 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 functionality of such packages is to manipulate developer reputation scores through automated publishing scripts. However, this specific package has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-namiresan86' originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which can lead to pollution of the npm registry. The continuous republishing of these variants can significantly affect developers' ability to trust the integrity of packages in the ecosystem, potentially leading to security breaches in applications that depend on these packages.

How To Fix

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

npm uninstall nokire-namiresan86

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, avoid using the 'nokire-namiresan86' package and monitor your project for any dependencies that may have been affected by this malicious package. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities. To check if your application is affected, you can visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'nokire-namiresan86' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for nokire-namiresan86 →

Share this vulnerability

FAQ

'nokire-namiresan86' is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially exposing your application to security risks.

You should uninstall the 'nokire-namiresan86' package immediately and monitor your project for any other affected dependencies.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

You can check if your application is affected by visiting the Vulert playground at Vulert Scanner, where you can analyze your package-lock.json.

How To Fix

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

npm uninstall nokire-namiresan86

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