Which versions of @b2b-frontend/store are malicious?

The following npm versions of @b2b-frontend/store are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @b2b-frontend/store if I installed it?

Remove @b2b-frontend/store 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 @b2b-frontend/store — how do I know if it already compromised me?

If @b2b-frontend/store 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 @b2b-frontend/store part of a known attack campaign?

Yes — @b2b-frontend/store is associated with the RLMA-2026-05824 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 @b2b-frontend/store across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @b2b-frontend/store (version 1.0.0).

Malicious package

@b2b-frontend/storenpm

Advisory published Aug 24, 2026Updated Sep 1, 2026

@b2b-frontend/store is a confirmed malicious npm package (MAL-2026-15675) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @b2b-frontend/store (npm)

MAL-2026-15675

Immediate action

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

npm uninstall @b2b-frontend/store

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

57f2064a6ffbc08510b3585434c02c44a4480002f2790b79f5d542e68db338f5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @b2b-frontend/store (version 1.0.0).
If you installed it — respond
Remove @b2b-frontend/store 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 @b2b-frontend/store 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-frontend/store on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05824

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @b2b-frontend/store-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