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

@b2b_blocker/show_activation_errornpm

Advisory published Updated

@b2b_blocker/show_activation_error is a confirmed malicious npm package (MAL-2026-3115) that executes malicious code on install (malicious version 99.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @b2b_blocker/show_activation_error (npm)

MAL-2026-3115
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @b2b_blocker/show_activation_error

What this malware does

The package @b2b_blocker/show_activation_error 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 '@b2b_blocker/show_activation_error' @ 99.0.3 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
99.0.3

Indicators of compromise (SHA-256)

c2481f85345c3760aa2b9b6fa5b39936a98d5826aa118ab22d19c02895c486d5
79dc8a9f5dac0334c50b1129f725d9f0c98e7c1085624d74c6172ade69db8417
92a7e6069d2adc1d4be44e27f549d35c648329ebf29b9ebd988a82d225cb4bcf

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @b2b_blocker/show_activation_error (version 99.0.3).

  2. If you installed it — respond

    Remove @b2b_blocker/show_activation_error 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 @b2b_blocker/show_activation_error 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. @b2b_blocker/show_activation_error on npm has been identified as a malicious package (version 99.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ppx3-ph2c-gqgm

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @b2b_blocker/show_activation_error-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

Explore

All malware advisories How O3 detects malware Vulnerability database
@b2b_blocker/show_activation_error (npm) malicious package — MAL-2026-3115 | O3 Security