Critical Malicious Code Vulnerability in @dev-blinq/blinqioclient Package
Summary
MAL-2025-191211: Malicious code in @dev-blinq/blinqioclient (npm). Affects @dev-blinq/blinqioclient versions 1.0.21. 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 @dev-blinq/blinqioclient package is an npm library designed for client-side interactions with the Blinq platform. It facilitates seamless communication and data exchange, making it a valuable tool for developers. However, its recent compromise has raised significant security concerns, exposing users to severe risks.
Vulnerability Detail
The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing sensitive tokens and credentials, which it subsequently publishes to GitHub. Additionally, it can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The worm poses a risk of destroying the user's home directory, making it a critical threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @dev-blinq/blinqioclientIf 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, consider removing the @dev-blinq/blinqioclient package from your project until a secure version is released. You can do this by executing: npm uninstall @dev-blinq/blinqioclient.
Conclusion
The @dev-blinq/blinqioclient package has been compromised by a malicious worm, posing significant risks to users. It is crucial to take immediate action by updating or removing the package to safeguard sensitive information and maintain system integrity.
See every vulnerability recorded for @dev-blinq/blinqioclient →
FAQ
The malicious code is part of an NPM worm that steals sensitive information and can propagate to other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
Immediately uninstall the package and check for any unauthorized access to your credentials or tokens.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
Failure to address this vulnerability could lead to unauthorized access to sensitive data, loss of control over your packages, and potential destruction of your home directory.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
