Which versions of bcp-security-update are malicious?

The following npm versions of bcp-security-update are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate bcp-security-update if I installed it?

Remove bcp-security-update 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 bcp-security-update — how do I know if it already compromised me?

If bcp-security-update 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 bcp-security-update part of a known attack campaign?

Yes — bcp-security-update is associated with the RLMA-2026-01118 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 bcp-security-update across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bcp-security-update (version 1.0.7).

Malicious package

bcp-security-updatenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

bcp-security-update is a confirmed malicious npm package (MAL-2026-1658) that executes malicious code on install (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bcp-security-update (npm)

MAL-2026-1658

Immediate action

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

npm uninstall bcp-security-update

What this malware does

The package bcp-security-update was found to contain malicious code.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

2026e2fed987ac227f60ffc50395c767c49b106f4e09751109e1fc71c5b6f59a

c9d8a18510bbeb71543526f0ef059351a12f97a1addd3c8664961231a7e862bf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01118

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks bcp-security-update-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