Malicious Code Injection in nokire-sekiya91: A Threat to npm Users

nokire-sekiya91 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163486: Malicious code in nokire-sekiya91 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

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

Vulnerability Detail

The vulnerability in 'nokire-sekiya91' originates from its malicious design, which includes scripts that modify 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 not only compromises the integrity of the npm registry but also exposes users to the risk of inadvertently using compromised 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-sekiya91

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 measure, you can avoid using the 'nokire-sekiya91' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The 'nokire-sekiya91' package represents a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.

See every vulnerability recorded for nokire-sekiya91 →

Share this vulnerability

FAQ

'nokire-sekiya91' is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.

Using 'nokire-sekiya91' can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall 'nokire-sekiya91' immediately using the command 'npm uninstall nokire-sekiya91' and audit your project for any other vulnerabilities.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall nokire-sekiya91

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