Which versions of bytefaas-sdk are malicious?

The following npm versions of bytefaas-sdk are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate bytefaas-sdk if I installed it?

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

If bytefaas-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is bytefaas-sdk part of a known attack campaign?

Yes — bytefaas-sdk is associated with the IN-MAL-2026-008119 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 bytefaas-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bytefaas-sdk (version 9999.0.0).

Malicious package

bytefaas-sdknpm

Advisory published Jul 8, 2026Updated Jul 8, 2026

bytefaas-sdk is a confirmed malicious npm package (MAL-2026-6993) that steals credentials and exfiltrates sensitive data (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bytefaas-sdk (npm)

MAL-2026-6993

Immediate action

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

npm uninstall bytefaas-sdk

What this malware does

Package published at version 9999.0.0 under the name bytefaas-sdk, the canonical dependency-confusion shape used to shadow a private internal package of the same name. package.json declares a preinstall hook that runs callback.js. On any npm install, callback.js collects the installer's os.hostname(), os.userInfo().username, platform, and cwd and transmits them to a third-party Interactsh (oast.fun) endpoint via both a DNS lookup (encoded subdomain) and an HTTPS POST. The HTTPS request sets rejectUnauthorized: false, disabling TLS certificate verification on the beacon. The package's README self-describes as a bug-bounty canary against TikTok's internal build systems, but the exfiltration fires unconditionally against any installer whose resolver picks up this public 9999.0.0 release — including unrelated organizations and CI systems. Cover-story framing does not change that non-consenting installers' host identifiers leak to a third-party server.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

07cb4f68cec68081ac4817ad2ae387e7b031d3377a74a74ecca59c5858940d08

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bytefaas-sdk (version 9999.0.0).
If you installed it — respond
bytefaas-sdk 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 bytefaas-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bytefaas-sdk on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008119

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bytefaas-sdk-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