Malicious Code Injection in okta-kue58-ruro Package

okta-kue58-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106635: Malicious code in okta-kue58-ruro (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 okta-kue58-ruro package is part of the npm ecosystem, typically used for various JavaScript applications. It is often utilized for task scheduling and job management in Node.js environments. However, this package has been identified as part of a malicious campaign that exploits npm's package management system, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts designed to modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and compromise the integrity of applications relying on this package.

How To Fix

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

npm uninstall okta-kue58-ruro

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, avoid using the okta-kue58-ruro package in your projects. Instead, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The okta-kue58-ruro package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and users. Immediate action is required to remove the package and safeguard applications from potential exploitation. Utilizing tools like Vulert can help in monitoring and addressing such vulnerabilities effectively.

See every vulnerability recorded for okta-kue58-ruro →

Share this vulnerability

FAQ

The okta-kue58-ruro package is an npm package used for task scheduling and job management in Node.js applications.

The vulnerability can lead to the injection of malicious code, potentially compromising your application's security and integrity.

You should uninstall the okta-kue58-ruro package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

If a patched version is released, it will be advisable to update to that version as soon as possible to mitigate the risks.

How To Fix

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

npm uninstall okta-kue58-ruro

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