Which versions of @asyncapi/react-component are malicious?

The following npm versions of @asyncapi/react-component are flagged malicious: 2.6.6, 2.6.7. Treat any of these as compromised.

How do I remediate @asyncapi/react-component if I installed it?

@asyncapi/react-component is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @asyncapi/react-component — how do I know if it already compromised me?

If @asyncapi/react-component 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 @asyncapi/react-component part of a known attack campaign?

Yes — @asyncapi/react-component is associated with the GHSA-62jw-fq3q-mxq5 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 @asyncapi/react-component 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 @asyncapi/react-component (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/react-component across your stack and pipelines.

Malicious package

@asyncapi/react-componentnpm

Malicious code in @asyncapi/react-component (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190642

Immediate action

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

npm uninstall @asyncapi/react-component

What this malware does

The package @asyncapi/react-component 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

2.6.62.6.7

Indicators of compromise (SHA-256)

16ad2626b282ceead75b7c40a43406b07085cca701cd9144ec3ec45301eeed5f

d9ebe88915a6eee986912a6566783764ff832588763eaa7b763710ed9f992299

991f71e5450234971d9918ae8ff264613789574cb85d2c847291a2bada90ea66

2a5c98f6b4dbe996df900be54fb063359087d18ffc1727d66898f55ea5bacb9f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @asyncapi/react-component (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/react-component across your stack and pipelines.
If you installed it — respond
@asyncapi/react-component is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @asyncapi/react-component 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 @asyncapi/react-component 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. @asyncapi/react-component on npm has been identified as a malicious package (versions 2.6.6, 2.6.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-62jw-fq3q-mxq5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @asyncapi/react-component-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring