Which versions of react-error-lint are malicious?

The following npm versions of react-error-lint are flagged malicious: 1.1.6. Treat any of these as compromised.

How do I remediate react-error-lint if I installed it?

react-error-lint is a typosquat — you almost certainly intended a legitimately-named package. Remove react-error-lint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed react-error-lint — how do I know if it already compromised me?

If react-error-lint was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is react-error-lint part of a known attack campaign?

Yes — react-error-lint is associated with the IN-MAL-2026-007012 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 react-error-lint across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-error-lint (version 1.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-error-lint across your stack and pipelines.

Malicious package

react-error-lintnpm

react-error-lint is a confirmed malicious npm package (MAL-2026-6137) that typosquats a legitimate package to trick installs (malicious version 1.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-error-lint (npm)

MAL-2026-6137

Immediate action

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

npm uninstall react-error-lint

What this malware does

Package name and README impersonate the popular react-error-boundary library (advertising an ErrorBoundary export, citing bvaughn and kentcdodds.com), but index.js exports unrelated helpers setDefaultModule and buildoptimize. The buildoptimize function issues an HTTP request to the hardcoded URL https://vercel-node-rouge-beta.vercel.app/icons/23 and passes the response body to eval(JSON.parse(b)) with no integrity check. Any caller that invokes buildoptimize() runs whatever JavaScript the attacker-controlled Vercel preview endpoint returns at that moment, granting remote code execution on the installer's machine. The advertised ErrorBoundary API does not exist, confirming the package is a lure rather than a misnamed legitimate library.

Malicious versions

1 flagged

1.1.6

Indicators of compromise (SHA-256)

a084c9e71eac856bf1a1fec025773cc561f9f6677c187d60e055b89c73d846b9

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-error-lint (version 1.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-error-lint across your stack and pipelines.
If you installed it — respond
react-error-lint is a typosquat — you almost certainly intended a legitimately-named package. Remove react-error-lint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If react-error-lint was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks react-error-lint before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. react-error-lint on npm has been identified as a malicious package (version 1.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007012

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-error-lint-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