Which versions of browser-compat-data are malicious?

The following npm versions of browser-compat-data are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate browser-compat-data if I installed it?

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

If browser-compat-data 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 browser-compat-data part of a known attack campaign?

Yes — browser-compat-data is associated with the RLMA-2026-01134 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 browser-compat-data across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for browser-compat-data (version 0.0.1).

Malicious package

browser-compat-datanpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

browser-compat-data is a confirmed malicious npm package (MAL-2026-1665) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in browser-compat-data (npm)

MAL-2026-1665

Immediate action

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

npm uninstall browser-compat-data

What this malware does

The package browser-compat-data was found to contain malicious code.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e33f2baef245b50858ef288c3286305cc6d88b3405810b8fc415c637f7964a9e

601776b12bb397ecad770ec5b29505afb8704042ffdb079640eb6f0f1903edab

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01134

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks browser-compat-data-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