Which versions of plugin-react-swc are malicious?

The following npm versions of plugin-react-swc are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate plugin-react-swc if I installed it?

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

If plugin-react-swc 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 plugin-react-swc part of a known attack campaign?

Yes — plugin-react-swc is associated with the GHSA-w743-w2hh-6f23, RLMA-2026-01498 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 plugin-react-swc 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 plugin-react-swc (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging plugin-react-swc across your stack and pipelines.

Malicious package

plugin-react-swcnpm

Malicious code in plugin-react-swc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-424

Immediate action

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

npm uninstall plugin-react-swc

What this malware does

The package plugin-react-swc was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

cba9afea98505469e9b9f36095ab566e5cd857b54255290d9defa67c40c62adb

197cedd065670a6a39b4401d52b2a636d5ff18f26c378b571770286a807ec467

8cdc34f6837f5000020cf619977261c8b0bdb5628a099dba55b0d3ff750c1d13

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for plugin-react-swc (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging plugin-react-swc across your stack and pipelines.
If you installed it — respond
Remove plugin-react-swc 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 plugin-react-swc 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 plugin-react-swc 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. plugin-react-swc on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w743-w2hh-6f23RLMA-2026-01498

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks plugin-react-swc-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