# MAL-2026-16320: Malicious code in @siriusbeyond/auth (npm)


- **Type:** Malicious package
- **Package:** `@siriusbeyond/auth` (npm)
- **Published:** 20 Sep 2026

## What is MAL-2026-16320?

MAL-2026-16320 is a malicious package in @siriusbeyond/auth, published on 20 Sep 2026. 

### Official description

Package @siriusbeyond/auth@99.0.0 registers both preinstall and postinstall lifecycle scripts that execute callback.js on every `npm install`. callback.js collects installer host identifiers (hostname, username, platform, cwd, homedir, CI/cloud indicators, npm registry) together with a filtered list of environment variable names matching token/secret/key/password/aws/npm/git patterns, and POSTs a Markdown report to https://api.telegram.org/bot<token>/sendMessage using a hardcoded bot token and chat_id 1064260758 embedded in the source. The lifecycle commands are wrapped in `2>/dev/null || true` to suppress errors and hide the beacon from install output. The version number 99.0.0 and private-scope name are the standard dependency-confusion shape targeting the `@siriusbeyond` scope, causing internal builds that reference that scope to resolve to this public package and beacon out. The package's self-description as a 'Dependency Confusion PoC / security research' does not change the runtime behavior: installer-owned data leaves every machine that installs it to an author-controlled Telegram channel.

The OpenSSF Package Analysis project identified '@siriusbeyond/auth' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

## What should I do about MAL-2026-16320?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-16320 is a malicious package: @siriusbeyond/auth (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-16320/ (Markdown: https://insights.sbomify.com/MAL-2026-16320/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-16320

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-16320/
Summaries are generated and may contain mistakes; the official description above is the record.