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

nokire-namiresan79 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163135: Malicious code in nokire-namiresan79 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'nokire-namiresan79' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores for token rewards but also poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-namiresan79' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the security and reliability of applications that depend on these packages. The malicious code is part of a broader trend of exploiting npm for personal gain, affecting developers and users alike.

How To Fix

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

npm uninstall nokire-namiresan79

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-namiresan79' package and replace it with a trusted alternative. Always review the packages you include in your project and consider using tools like Vulert to monitor for vulnerabilities in your dependencies.

Conclusion

The 'nokire-namiresan79' package represents a significant threat to the npm ecosystem due to its malicious behavior. By understanding the nature of this vulnerability and taking proactive steps to remove affected packages, developers can protect their applications and maintain the integrity of their software environments.

See every vulnerability recorded for nokire-namiresan79 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and repopulates the npm registry with harmful variants.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately using 'npm uninstall nokire-namiresan79' and review your project's dependencies for any other vulnerabilities.

Yes, you should look for trusted and well-maintained 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-namiresan79

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