Which versions of pretty-tabulate are malicious?

The following PyPI versions of pretty-tabulate are flagged malicious: 2.37.1, 2.37.2. Treat any of these as compromised.

How do I remediate pretty-tabulate if I installed it?

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

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

Yes — pretty-tabulate is associated with the 2026-03-color-list 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 pretty-tabulate 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 pretty-tabulate (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pretty-tabulate across your stack and pipelines.

Malicious package

pretty-tabulatePyPI

Malicious code in pretty-tabulate (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1480

Immediate action

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

pip uninstall pretty-tabulate

What this malware does

Malicious code hidden in the color-list package uses the presence of pretty-tabulate as a trigger to load code hidden in likely a third malicious package. Packages were published simultaneously by two accounts not used for about a year, suggesting hijacked access.

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

Campaign: 2026-03-color-list

Reasons (based on the campaign):

The malicious code is intentionally included in a dependency of the package
obfuscation

Malicious versions

2 flagged

2.37.12.37.2

Indicators of compromise (SHA-256)

807e99c43a51fb7620cee47a356774c3ead94e75c4bc48621a942c835107b2eb

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

Campaign

2026-03-color-list

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pretty-tabulate-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