Which versions of byte-parser are malicious?

The following npm versions of byte-parser are flagged malicious: 1.1.0, 1.2.0. Treat any of these as compromised.

How do I remediate byte-parser if I installed it?

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

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

Yes — byte-parser is associated with the GHSA-wfmp-rqvg-5fjr 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 byte-parser 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 byte-parser (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging byte-parser across your stack and pipelines.

Malicious package

byte-parsernpm

Malicious code in byte-parser (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3846

Immediate action

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

npm uninstall byte-parser

What this malware does

Part of the Mini Shai-Hulud supply chain attack campaign in which a threat actor compromised the npm account atool and published 631 malicious versions across 314 npm packages in an automated 22-minute burst. Each malicious version injects a preinstall hook that executes a 498KB obfuscated Bun script, using the GitHub API as a covert exfiltration channel. Credentials are committed to attacker-controlled repositories following Dune-themed naming patterns (e.g., harkonnen-melange-742). Stolen data includes AWS keys, GitHub PATs, npm tokens, GCP service accounts, Azure credentials, Kubernetes service account tokens, SSH keys, Docker auth configs, database connection strings, Stripe keys, and Slack tokens. Malicious versions also establish persistence via CI/CD workflow injection (a GitHub Actions workflow named Run Copilot dumps all secrets via toJSON(secrets)), AI agent session hooks, and a system daemon named kitty-monitor.

This specific package (byte-parser) was modified to include a malicious preinstall hook executing the obfuscated Bun payload.

The package byte-parser was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised as part of the ongoing "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

2 flagged

1.1.01.2.0

Indicators of compromise (SHA-256)

ffab22689007686aed902c7d7c1b63b3f17f53a1f54fe99866337e2c99d68ea6

847ef6b381d410bf176f7414a6f0fbbcf46a5f39b6d9011e126b279bd2d781df

b679fb7a125db6448ded665d468f5e0220314660e5dfa83874b6553433475c25

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

Campaign

GHSA-wfmp-rqvg-5fjr

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks byte-parser-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