MAL-2026-16343 Malicious code in siriusbeyond (npm)
Malicious package
Published
MAL-2026-16343 is a malicious package: siriusbeyond (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16343/ (Markdown: https://insights.sbomify.com/MAL-2026-16343/index.md)
- Package
- siriusbeyond
- Registry
- npm
What is MAL-2026-16343?
MAL-2026-16343 is a malicious package in siriusbeyond, published on 21 Sep 2026.
Official description
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.What should I do about MAL-2026-16343?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.