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

nokire-namiresan22 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163073: Malicious code in nokire-namiresan22 (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 package 'nokire-namiresan22' is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The malicious nature of this package lies in its ability to alter critical files and continuously republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-namiresan22' originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall nokire-namiresan22

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

Currently, the best workaround is to avoid using the 'nokire-namiresan22' package altogether. If it is already in use, ensure to uninstall it immediately and monitor your project for any other potentially malicious packages.

Conclusion

The 'nokire-namiresan22' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and remove such packages from their projects to maintain the integrity and security of their applications. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities effectively.

See every vulnerability recorded for nokire-namiresan22 →

Share this vulnerability

FAQ

'nokire-namiresan22' is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the modification of your package.json file, potentially exposing your application to further security risks and instability.

You should uninstall the package immediately using 'npm uninstall nokire-namiresan22' and check your project for any other malicious packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall nokire-namiresan22

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