Which versions of bcp-security-updates are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for bcp-security-updates (version 1.0.8).

Malicious package

bcp-security-updatesnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in bcp-security-updates (npm)

MAL-2026-1659

Immediate action

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

npm uninstall bcp-security-updates

What this malware does

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

Malicious versions

1 flagged

1.0.8

Indicators of compromise (SHA-256)

fdb145341159df1fae9d26fea2346445a0cfe602517879d2b6b1dba8788e9913

0ae78f7be7d7bfc2a5c001fd71b000a7cfe42a5f8c6e7d2b828ec3f143d26319

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01119

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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