Which versions of bytefrontier-partner are malicious?

The following npm versions of bytefrontier-partner are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate bytefrontier-partner if I installed it?

Remove bytefrontier-partner from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed bytefrontier-partner — how do I know if it already compromised me?

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

Yes — bytefrontier-partner is associated with the GHSA-9f9x-w4j9-p76g 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 bytefrontier-partner 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 bytefrontier-partner (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytefrontier-partner across your stack and pipelines.

Malicious package

bytefrontier-partnernpm

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

MAL-2026-2423

Immediate action

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

npm uninstall bytefrontier-partner

What this malware does

The package bytefrontier-partner 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.

The OpenSSF Package Analysis project identified 'bytefrontier-partner' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

d271c5a87554c0cd5b76476e42c6bd33507d9873da12b465c4eb7c19b73eeeda

a6b7c067c478263090ed1c2af69f93fb08ed460a91f5e70203c0de2037710507

6d9b347a5cc823261d983a3b7d4f5332791f93a620a772dfd6927c62f72ac5fa

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bytefrontier-partner (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytefrontier-partner across your stack and pipelines.
If you installed it — respond
Remove bytefrontier-partner from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bytefrontier-partner 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 bytefrontier-partner 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. bytefrontier-partner on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9f9x-w4j9-p76g

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks bytefrontier-partner-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring