Which versions of siriusbeyond are malicious?

The following npm versions of siriusbeyond are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate siriusbeyond if I installed it?

siriusbeyond 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 — how do I know if it already compromised me?

If siriusbeyond was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is siriusbeyond part of a known attack campaign?

Yes — siriusbeyond is associated with the IN-MAL-2026-020220 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 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for siriusbeyond (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging siriusbeyond across your stack and pipelines.

Malicious package

siriusbeyondnpm

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

Malicious code in siriusbeyond (npm)

MAL-2026-16343

Immediate action

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

npm uninstall siriusbeyond

What this malware does

package.json wires callback.js to both the preinstall and postinstall lifecycle hooks, so npm install siriusbeyond executes it automatically. callback.js collects hostname, username, platform, cwd, home directory, uid/gid/pid, network interface details, CI/cloud environment indicators, and a list of process.env variable names matching approximately 35 credential-shaped regexes (token, secret, key, password, aws, azure, gcp, npm, git, ssh, jwt, database, stripe, slack, discord, webhook, etc.), together with existence checks for.env,.npmrc, credentials, and secrets.json in the working directory. The collected payload is POSTed to api.telegram.org using a hardcoded bot token and chat id (chat 1064260758). A secondary channel base64-encodes a JSON blob of host, user, and CI fields and issues a dns.resolve() against <base64>.dc-callback.example.com, providing a DNS-tunnel exfil path when outbound HTTPS is blocked. Even though variable values are not sent, the disclosed variable names and credential-file inventory identify which secrets the installer holds and enable targeted follow-on attack.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6ce19ca17a48cf79dd094940533d1bff88413d44c945948d0041da15a5b61779

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for siriusbeyond (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging siriusbeyond across your stack and pipelines.
If you installed it — respond
siriusbeyond 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 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks siriusbeyond before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. siriusbeyond on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020220

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks siriusbeyond-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