Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @teselagen published 10 malicious packages. See the full campaign →
Malicious package

@teselagen/react-tablenpm

@teselagen/react-table is a confirmed malicious npm package (MAL-2025-47278) that steals credentials and exfiltrates sensitive data (malicious versions 6.10.19, 6.10.20, 6.10.21…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @teselagen/react-table (npm)

MAL-2025-47278
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @teselagen/react-table

What this malware does

The package was compromised and malicious code added.

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 Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

4 flagged
6.10.196.10.206.10.216.10.22

Indicators of compromise (SHA-256)

35f0735aa86d1091b1512a81fb01bb052f137bb071faaadd8c7e0713abac239b
0fe097a3b9857df606aa7c6e648a5990916eeea8472e94ce8b16b0ab68ecb8f1
e9e8d3b8d609d58a15f146ff00a8e8e7376bb4a738a74334361bc6a29a3763b3
a4e8f8022d4dcec4a9cb1b60e9428ddd3c38a67329174412b17281de5116dc57

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 @teselagen/react-table (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @teselagen/react-table across your stack and pipelines.

  2. If you installed it — respond

    @teselagen/react-table 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 @teselagen/react-table 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 @teselagen/react-table 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. @teselagen/react-table on npm has been identified as a malicious package (versions 6.10.19, 6.10.20, 6.10.21, 6.10.22 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m46j-8g4g-f7hg

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@teselagen/react-table (npm) malicious package — MAL-2025-47278 | O3 Security