Critical Malicious Code Vulnerability in @oku-ui/presence Package
Summary
MAL-2025-191265: Malicious code in @oku-ui/presence (npm). Affects @oku-ui/presence versions 0.6.2. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @oku-ui/presence package is a utility library in the npm ecosystem designed to manage UI presence states in web applications. It provides functionalities that help developers create responsive and interactive user interfaces. However, this package has been compromised, exposing users to severe security risks.
Vulnerability Detail
The vulnerability originates from a malicious NPM worm known as Sha1-Hulud: The Second Coming. This worm compromises the package by embedding malicious code that steals tokens and credentials, subsequently publishing them to GitHub. The worm can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. Additionally, it poses a risk of destroying the user's home directory, leading to potential data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @oku-ui/presenceIf 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 can remove the @oku-ui/presence package from their project until a secure version is confirmed. Use the command: npm uninstall @oku-ui/presence.
Conclusion
The @oku-ui/presence package has been compromised by a malicious worm that poses significant security risks. Users are strongly advised to update to the latest version or remove the package until a secure version is available. Monitoring tools like Vulert can help keep your projects safe from such vulnerabilities.
See every vulnerability recorded for @oku-ui/presence →
FAQ
The malicious code is designed to steal sensitive tokens and credentials from users and publish them to GitHub.
The worm can infect other NPM packages owned by the user, spreading the malicious code further.
The risks include unauthorized access to sensitive information, potential data loss, and the compromise of other NPM packages.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
