Which versions of tableasets are malicious?

The following PyPI versions of tableasets are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate tableasets if I installed it?

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

If tableasets was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is tableasets part of a known attack campaign?

Yes — tableasets is associated with the 2025-11-spellcheckers 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 tableasets across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tableasets (version 1.0.1).

Part of a larger attack: 2025-11-spellcheckers published 28 malicious packages. See the full campaign →

Malicious package

tableasetsPyPI

Advisory published Jan 29, 2026Updated Oct 30, 2026

tableasets is a confirmed malicious PyPI package (MAL-2026-602) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tableasets (PyPI)

MAL-2026-602

Immediate action

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

pip uninstall tableasets

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

3144974fea7e1e56465e9ba49f98ab0457b3adf75130300002c47f415d64fbd0

107940f53103c9600bc77b41bf3f43807c7a4dac58eea514ff34291f2f691452

2e6ed9a37dc3a0d775fe4576b0cc9ce08b8e3287f1cb717ccc3191ef6e32f997

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tableasets (version 1.0.1).
If you installed it — respond
tableasets 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 tableasets was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tableasets on PyPI 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

2025-11-spellcheckers

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database