Which versions of bic-seo are malicious?

The following npm versions of bic-seo are flagged malicious: 2.0.3. Treat any of these as compromised.

How do I remediate bic-seo if I installed it?

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

If bic-seo 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 bic-seo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bic-seo (version 2.0.3).

Malicious package

bic-seonpm

Advisory published Mar 20, 2026Updated Mar 23, 2026

bic-seo is a confirmed malicious npm package (MAL-2026-1995) that executes malicious code on install (malicious version 2.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bic-seo (npm)

MAL-2026-1995

Immediate action

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

npm uninstall bic-seo

What this malware does

The package bic-seo was found to contain malicious code.

The OpenSSF Package Analysis project identified 'bic-seo' @ 2.0.3 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

2.0.3

Indicators of compromise (SHA-256)

7eeaff4f3318ed34f500a278b37ae6e39604797f0de8643056247dc4ab1ebc15

88b87b18acc3a062d6a79eb7fd959cbbfea586694cf6d918aac1ddacaa062518

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bic-seo (version 2.0.3).
If you installed it — respond
Remove bic-seo 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 bic-seo 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. bic-seo on npm has been identified as a malicious package (version 2.0.3 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 bic-seo-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