Which versions of tableates are malicious?

The following PyPI versions of tableates are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6. Treat any of these as compromised.

How do I remediate tableates if I installed it?

tableates 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 tableates — how do I know if it already compromised me?

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

Yes — tableates is associated with the 2025-11-spellcheckers, RLMA-2026-00801 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 tableates 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 tableates (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tableates across your stack and pipelines.

Malicious package

tableatesPyPI

Malicious code in tableates (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-492

Immediate action

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

pip uninstall tableates

What this malware does

Packages contain hidden code that is effectively run during importing or using the library, and downloads second stage code. Then, a process running in background periodically connects to a remote host and waits for next code to execute

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-11-spellcheckers

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

6 flagged

1.0.11.0.21.0.31.0.41.0.51.0.6

Indicators of compromise (SHA-256)

c69d9a3e244227f4e4146b60829ead907656c47989b3b83e1e5f56a2c06064ff

5a8919788006840612f4bfd881d7fdf82ca62a2dd06118ee99f95f1e4b58d4e4

86d83c5da161b2b46a739b6aa32c4c53f00a83005d767ce5fbab1ef9e796eb23

32af1b264b13fe7b0871495d3893aa755750bb3295157df3893053e12bb69332

a2e615bd9e46250348c3f1a6e688fede60bc297ba28cd13b1b0043f4e1e144f0

ce121c5b26cc5d9b73c0fda2ed81ad594b6af77ff4943990f6edda3d3f46f906

56bf81438578d2b6a6b54e86e1214a5b26c09627c0a28fa54e1643afe75aa6a2

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 tableates (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tableates across your stack and pipelines.
If you installed it — respond
tableates 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 tableates 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 tableates 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. tableates on PyPI has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-spellcheckersRLMA-2026-00801

References

Credits

Kamil Mańkowski (kam193) · analyst
ReversingLabs · finder

Detect & block this

O3 blocks tableates-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