NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@dev-blinq/ui-systemsnpm

Advisory published Updated

@dev-blinq/ui-systems is a confirmed malicious npm package (MAL-2025-191214) that steals credentials and exfiltrates sensitive data (malicious version 1.0.93). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dev-blinq/ui-systems (npm)

MAL-2025-191214
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @dev-blinq/ui-systems

What this malware does

The package @dev-blinq/ui-systems was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
1.0.93

Indicators of compromise (SHA-256)

2dcadea46bca58635650df7ad71a2ea7d3f45142168ac26f0bc4325588ab175e
e0a91b996dfdd7b43709435dd4dedcde7dc2d6d3f5b89229dfc9a21ca3a01f00
9ce530512b608913637db50ce0058d08d5afb8173c8b5968023c9b9665bcde49

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @dev-blinq/ui-systems (version 1.0.93).

  2. If you installed it — respond

    @dev-blinq/ui-systems is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @dev-blinq/ui-systems was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @dev-blinq/ui-systems on npm has been identified as a malicious package (version 1.0.93 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ccc8-rh82-3xvr

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @dev-blinq/ui-systems-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@dev-blinq/ui-systems (npm) malicious package — MAL-2025-191214 | O3 Security