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

nokire-namiresan44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163097: Malicious code in nokire-namiresan44 (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-namiresan44' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often flooding the registry with numerous derivative packages. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'nokire-namiresan44' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to a polluted npm registry. The malicious payload can compromise the security of applications relying on these packages, potentially introducing further vulnerabilities and instability.

How To Fix

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

npm uninstall nokire-namiresan44

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 'nokire-namiresan44' and any other packages associated with the tea.xyz token reward campaign. Additionally, you can use the following command to uninstall the package: npm uninstall nokire-namiresan44.

Conclusion

The 'nokire-namiresan44' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is essential for developers to be vigilant, remove any compromised packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for nokire-namiresan44 →

Share this vulnerability

FAQ

'nokire-namiresan44' is an npm package linked to a malicious campaign that floods the npm registry with derivative packages to manipulate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and stability.

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

If you have used 'nokire-namiresan44', it is recommended to uninstall it immediately and review your application's dependencies for any other compromised packages.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

How To Fix

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

npm uninstall nokire-namiresan44

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