NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bytefrontier-partnernpm

Advisory published Updated

bytefrontier-partner is a confirmed malicious npm package (MAL-2026-2423) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bytefrontier-partner (npm)

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
  1. Find it

    Search your lockfiles and build artifacts for bytefrontier-partner (version 99.0.0).

  2. 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.

  3. Did it already run?

    If bytefrontier-partner 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. 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

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.

Explore

bytefrontier-partner (npm) malicious package — MAL-2026-2423 | O3 Security