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

nokire-sekiya94 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163489: Malicious code in nokire-sekiya94 (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 nokire-sekiya94 package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify the package.json file, removing private flags and altering version numbers, which can lead to significant security risks for users relying on this package.

Vulnerability Detail

The vulnerability in the nokire-sekiya94 package originates from its association with a campaign that floods the npm registry with malicious packages. It contains scripts that automatically publish variants of itself, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The malicious payload alters the package.json file, which can lead to unauthorized access and manipulation of the package, exposing users to further risks.

How To Fix

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

npm uninstall nokire-sekiya94

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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. You can also use the following command to uninstall the package: npm uninstall nokire-sekiya94.

Conclusion

The nokire-sekiya94 package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the npm registry. Users are advised to uninstall this package immediately and utilize tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for nokire-sekiya94 →

Share this vulnerability

FAQ

The nokire-sekiya94 package is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can compromise the integrity of your application by allowing unauthorized modifications to the package.json file, potentially leading to security breaches.

You should immediately uninstall the nokire-sekiya94 package and check for any updates or patches that may be available.

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

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall nokire-sekiya94

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