Which versions of bytecraft are malicious?

The following npm versions of bytecraft are flagged malicious: 1.5.0, 2.0.0. Treat any of these as compromised.

How do I remediate bytecraft if I installed it?

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

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

Yes — bytecraft is associated with the RLMA-2026-05504, IN-MAL-2026-013184, IN-MAL-2026-013181, RLUA-2026-06103 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 bytecraft 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 bytecraft (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytecraft across your stack and pipelines.

Malicious package

bytecraftnpm

bytecraft is a confirmed malicious npm package (MAL-2026-10891) that steals credentials and exfiltrates sensitive data (malicious versions 1.5.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bytecraft (npm)

MAL-2026-10891

Immediate action

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

npm uninstall bytecraft

What this malware does

No suspicious behavior was identified in this version of bytecraft. There is no evidence of install-time network activity, lifecycle scripts fetching remote code, credential access, environment scraping, hardcoded exfiltration endpoints, or other supply-chain attack patterns. The package appears to be a normal library release.

Malicious versions

2 flagged

1.5.02.0.0

Indicators of compromise (SHA-256)

ea6749c0d90490ce1d96256089ac367d4f8ed4fd41c05366fcd20066e4dfffdb

5019255f92ddbba1d16121932a97c3dded3479048dea28e835e67751613a7e04

55b4433b369e2ff82bc33b11110ddfa63c15a2d685bf3484fb37092ae4bd077f

fb9bfa4e98ba9decd2bf6acacb0af852d6c086c1bcf7d3c08cf8794b97944002

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 bytecraft (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytecraft across your stack and pipelines.
If you installed it — respond
bytecraft 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 bytecraft 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 bytecraft 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. bytecraft on npm has been identified as a malicious package (versions 1.5.0, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05504IN-MAL-2026-013184IN-MAL-2026-013181RLUA-2026-06103

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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