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

nokire-rara54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163344: Malicious code in nokire-rara54 (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 package nokire-rara54 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in nokire-rara54 originates from its association with a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names to republish variants continuously. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security breaches and reputation damage within the npm ecosystem.

How To Fix

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

npm uninstall nokire-rara54

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-rara54 package altogether. If it is a dependency of another package, consider using an alternative package that does not have known vulnerabilities.

Conclusion

The nokire-rara54 package poses a significant threat due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package from their projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for nokire-rara54 →

Share this vulnerability

FAQ

Nokire-rara54 is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for token rewards.

If you have nokire-rara54 installed, your project may be at risk of security breaches and could inadvertently contribute to the pollution of the npm registry.

You should uninstall nokire-rara54 immediately and check for any dependencies that may rely on it. Update your project accordingly.

Currently, there is no patched version available for nokire-rara54. The best course of action is to remove the package from your project.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

How To Fix

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

npm uninstall nokire-rara54

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