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

nokire-rara41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163330: Malicious code in nokire-rara41 (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-rara41' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards related to the tea protocol.

Vulnerability Detail

The vulnerability in 'nokire-rara41' stems from its inclusion in a malicious campaign that deploys autopublish scripts. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall nokire-rara41

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 manually remove the 'nokire-rara41' package from your project by executing the command: npm uninstall nokire-rara41. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The 'nokire-rara41' package represents a significant threat due to its malicious intent to manipulate the npm registry. 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 exploitation.

See every vulnerability recorded for nokire-rara41 →

Share this vulnerability

FAQ

'nokire-rara41' is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

You should immediately uninstall the package using 'npm uninstall nokire-rara41' and check for any other affected packages.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall nokire-rara41

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