Critical Malicious Code Vulnerability in @oku-ui/progress Package

@oku-ui/progress Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191268: Malicious code in @oku-ui/progress (npm). Affects @oku-ui/progress versions 0.6.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @oku-ui/progress package is a JavaScript library used in web development to create progress indicators. It is part of the Oku UI framework, which provides a set of components for building user interfaces. This package is widely used in various applications, making it a significant target for malicious actors. The vulnerability in question stems from a compromise that allows attackers to inject malicious code into the package, posing severe risks to users and their applications.

Vulnerability Detail

The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which compromised the @oku-ui/progress package. This malicious payload is designed to steal tokens and credentials from users, subsequently publishing this sensitive information to GitHub. Additionally, the worm can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. There is also a risk that the worm may destroy the user's home directory, leading to significant data loss.

How To Fix

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

npm uninstall @oku-ui/progress

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, users are advised to remove the @oku-ui/progress package from their projects until a secure version is released. You can uninstall the package using the following command: npm uninstall @oku-ui/progress.

Conclusion

The @oku-ui/progress package has been compromised by a malicious worm that poses significant risks to users. Immediate action is required to update or remove the package to safeguard sensitive information. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for @oku-ui/progress →

Share this vulnerability

FAQ

The vulnerability involves malicious code that steals user tokens and credentials, potentially leading to unauthorized access and data breaches.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.

Detailed information can be found on the GitHub repository for malicious packages or through security advisories related to the NPM ecosystem.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall @oku-ui/progress

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