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

nokire-namiresan89 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163146: Malicious code in nokire-namiresan89 (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-namiresan89' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-namiresan89' originates from its malicious design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. The ramifications include compromised package integrity, potential security risks for users, and degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall nokire-namiresan89

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 workaround, you can avoid using the 'nokire-namiresan89' package altogether. If it is already in use, consider removing it from your dependencies and replacing it with a secure alternative. You can do this by running: npm uninstall nokire-namiresan89.

Conclusion

The 'nokire-namiresan89' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and stay vigilant about potential vulnerabilities in their dependencies.

See every vulnerability recorded for nokire-namiresan89 →

Share this vulnerability

FAQ

'nokire-namiresan89' is an npm package associated with a token reward campaign that manipulates the npm registry.

The vulnerability can compromise the integrity of your application by introducing malicious code and polluting the npm registry.

You should uninstall 'nokire-namiresan89' immediately and check for any potential impacts on your application.

Currently, there is no specific patch for 'nokire-namiresan89', but it is advisable to monitor the npm registry for updates.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall nokire-namiresan89

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