MAL-2026-16326 Malicious code in byted-commerce-materials (npm)
Malicious package
Published
MAL-2026-16326 is a malicious package: byted-commerce-materials (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-16326/ (Markdown: https://insights.sbomify.com/MAL-2026-16326/index.md)
- Package
- byted-commerce-materials
- Registry
- npm
What is MAL-2026-16326?
MAL-2026-16326 is a malicious package in byted-commerce-materials, published on 21 Sep 2026.
Official description
package.json declares both preinstall and postinstall running
node callback.js, so the payload fires automatically on npm install. callback.js collects hostname, username, platform, cwd, home directory, network interfaces, uid/gid, CI/cloud provider fingerprints, and probes the working directory for credential files (.env,.npmrc,.yarnrc,.git/config,.docker/config.json, credentials, secrets.json). It also enumerates process.env keys and filters them against a broad credential-name regex set (token, secret, key, password, aws, azure, gcp, npm, ssh, private, credential, jwt, bearer, stripe, db, mysql, postgres, mongo, redis). The collected payload is POSTed to api.telegram.org via a hardcoded Telegram Bot API token and chat_id (1064260758). A secondary DNS-based side channel base64-encodes host/user/CI fields and issues a dns.resolve against a <encoded>.dc-callback.example.com subdomain as a fallback for environments that block HTTPS to Telegram. The package presents itself as a byted/commerce materials module and a security research / dependency confusion PoC; the self-label does not change that the traced behavior harvests installer host and credential reconnaissance and ships it off-host to attacker-controlled channels without consent.What should I do about MAL-2026-16326?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.