Which versions of bis-schemas are malicious?

The following npm versions of bis-schemas are flagged malicious: 9.99.9. Treat any of these as compromised.

How do I remediate bis-schemas if I installed it?

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

If bis-schemas 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 bis-schemas part of a known attack campaign?

Yes — bis-schemas is associated with the RLMA-2026-01125 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 bis-schemas across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bis-schemas (version 9.99.9).

Malicious package

bis-schemasnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

bis-schemas is a confirmed malicious npm package (MAL-2026-1660) that executes malicious code on install (malicious version 9.99.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bis-schemas (npm)

MAL-2026-1660

Immediate action

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

npm uninstall bis-schemas

What this malware does

The package bis-schemas was found to contain malicious code.

Malicious versions

1 flagged

9.99.9

Indicators of compromise (SHA-256)

8d325a1952d5cedd2f2e27f3a4d489741b51f020b012688445b8aeed6e0a0268

3a67881a70b43bbe32ec81fae7fa44c55b0b4c665ffc331c38a1cd73206c60f7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01125

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks bis-schemas-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