Which versions of byted-commerce-materials are malicious?

The following npm versions of byted-commerce-materials are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate byted-commerce-materials if I installed it?

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

If byted-commerce-materials 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 byted-commerce-materials part of a known attack campaign?

Yes — byted-commerce-materials is associated with the IN-MAL-2026-020221 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 byted-commerce-materials 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 byted-commerce-materials (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 byted-commerce-materials across your stack and pipelines.

Malicious package

byted-commerce-materialsnpm

byted-commerce-materials is a confirmed malicious npm package (MAL-2026-16326) 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 byted-commerce-materials (npm)

MAL-2026-16326

Immediate action

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

npm uninstall byted-commerce-materials

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f777e32b4a6cbb7f91f7fcac050a02a73e356df1c87e7dcd985ea9172a3993da

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 byted-commerce-materials (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 byted-commerce-materials across your stack and pipelines.
If you installed it — respond
byted-commerce-materials 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 byted-commerce-materials 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 byted-commerce-materials 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. byted-commerce-materials 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-020221

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks byted-commerce-materials-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