Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

react-autolink-textnpm

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

MAL-2026-2214
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-autolink-text

What this malware does

The package react-autolink-text was found to contain malicious code.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

1 flagged
2.0.1

Indicators of compromise (SHA-256)

fd177fa79b8a260462e6d401664042f531b87c717ab56490caf1a3d4642181c3
402f7d8c6db956de1c20cce1c23b9d2585a9210f6aae7859acb956fb66728010

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    react-autolink-text 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.

  3. Did it already run?

    If react-autolink-text 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.

  4. How O3 protects you

    O3 blocks react-autolink-text 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-autolink-text on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

react-autolink-text (npm) malicious package — MAL-2026-2214 | O3 Security