Malicious Code Injection in nokire-rara47: A Threat to npm Ecosystem

nokire-rara47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163336: Malicious code in nokire-rara47 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokire-rara47' 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 creating numerous derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious behavior of this package poses a significant risk to developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-rara47' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall nokire-rara47

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

Conclusion

The 'nokire-rara47' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for nokire-rara47 →

Share this vulnerability

FAQ

'nokire-rara47' is a malicious npm package that is part of a campaign to manipulate the npm registry by generating numerous derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

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

Regularly audit your dependencies, use trusted packages, and keep your packages updated to their latest versions.

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

How To Fix

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

npm uninstall nokire-rara47

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