Which versions of @siriusbeyond/ui are malicious?

The following npm versions of @siriusbeyond/ui are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @siriusbeyond/ui if I installed it?

@siriusbeyond/ui 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.

I already installed @siriusbeyond/ui — how do I know if it already compromised me?

If @siriusbeyond/ui 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.

Is @siriusbeyond/ui part of a known attack campaign?

Yes — @siriusbeyond/ui is associated with the IN-MAL-2026-020218 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @siriusbeyond/ui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @siriusbeyond/ui (version 99.0.0).

Malicious package

@siriusbeyond/uinpm

Advisory published Sep 21, 2026Updated Sep 21, 2026

@siriusbeyond/ui is a confirmed malicious npm package (MAL-2026-16321) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @siriusbeyond/ui (npm)

MAL-2026-16321

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @siriusbeyond/ui

What this malware does

On npm install, both preinstall and postinstall lifecycle hooks execute callback.js, which collects installer host identity (hostname, username, platform, cwd, home directory, UID, CI/cloud indicators, npm registry) and enumerates the names of environment variables matching credential-shaped patterns (token, secret, key, password, auth, api, aws, azure, npm, git, docker, registry, artifactory, nexus, credential), then POSTs the collected data to api.telegram.org via a hardcoded bot token and chat id (1064260758) using https.request to /bot<token>/sendMessage. The lifecycle commands are wrapped in 2>/dev/null || true to suppress errors and hide the exfil from the installer during npm install. A README framing this as a dependency-confusion proof of concept does not change the behavior: the package auto-executes credential-context reconnaissance and host fingerprinting against installer machines and transmits the results to an attacker-controlled Telegram channel.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

3d81713c34940a8d3511a53c6cb8001481734bc2493be23d0f6ddb1dd561fa72

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @siriusbeyond/ui (version 99.0.0).
If you installed it — respond
@siriusbeyond/ui 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.
Did it already run?
If @siriusbeyond/ui 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. @siriusbeyond/ui on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020218

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @siriusbeyond/ui-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