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

nokire-sekiya7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163462: Malicious code in nokire-sekiya7 (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 nokire-sekiya7 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the nokire-sekiya7 package originates from its association with the tea.xyz token reward campaign. This package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, which can lead to a compromised npm registry and potential security risks for developers relying on these packages.

How To Fix

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

npm uninstall nokire-sekiya7

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-sekiya7 package and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The nokire-sekiya7 package poses a significant threat to npm users due to its malicious code designed to exploit the npm publishing system. It is crucial to remove this package and any associated dependencies to protect your projects from potential security risks.

See every vulnerability recorded for nokire-sekiya7 →

Share this vulnerability

FAQ

The nokire-sekiya7 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing untrusted code.

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

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.

There is no patch for the nokire-sekiya7 package as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall nokire-sekiya7

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