What does the bps-design-system malware do?

The package bps-design-system was found to contain malicious code. The OpenSSF Package Analysis project identified 'bps-design-system' @ 25.11.88 (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.

Which versions of bps-design-system are malicious?

The following npm versions of bps-design-system are flagged malicious: 25.11.88. Treat any of these as compromised.

How do I remediate bps-design-system if I installed it?

Remove bps-design-system 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 bps-design-system — how do I know if it already compromised me?

If bps-design-system 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.

How do I find bps-design-system across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bps-design-system (version 25.11.88).

Malicious package

bps-design-systemnpm

Advisory published Feb 28, 2026Updated Mar 1, 2026

bps-design-system is a confirmed malicious npm package (MAL-2026-1087) that executes malicious code on install (malicious version 25.11.88). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bps-design-system (npm)

MAL-2026-1087

Immediate action

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

npm uninstall bps-design-system

What this malware does

The package bps-design-system was found to contain malicious code.

The OpenSSF Package Analysis project identified 'bps-design-system' @ 25.11.88 (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

25.11.88

Indicators of compromise (SHA-256)

f8ef5089934a6863cb12ab39ed765246f29c073c3cb1291a16d865d4a8656a86

1f41e4d6abfba5f03e914140b0b171314ef8a614e3e03ff9685325532260a745

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks bps-design-system-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