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

nokire-namiresan71 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163127: Malicious code in nokire-namiresan71 (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-namiresan71' is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious behavior includes altering package metadata and continuously republishing variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-namiresan71' stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall nokire-namiresan71

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-namiresan71' package and monitor your project for any dependencies that may have inadvertently included it. Regularly check your package-lock.json file for any suspicious entries and remove any malicious packages.

Conclusion

The 'nokire-namiresan71' package poses a significant threat to the integrity of the npm ecosystem due to its malicious behavior. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential risks associated with malicious packages.

See every vulnerability recorded for nokire-namiresan71 →

Share this vulnerability

FAQ

'nokire-namiresan71' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of derivative packages.

Using 'nokire-namiresan71' can lead to the inclusion of malicious code in your project, potentially compromising security and integrity.

You should uninstall 'nokire-namiresan71' immediately using 'npm uninstall nokire-namiresan71' and review your project for any other malicious dependencies.

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

Yes, tools like Vulert can help you monitor your npm packages for vulnerabilities in real-time, ensuring that your project remains secure.

How To Fix

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

npm uninstall nokire-namiresan71

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