Which versions of tomli-dzw are malicious?

The following PyPI versions of tomli-dzw are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tomli-dzw if I installed it?

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

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

Yes — tomli-dzw is associated with the RLMA-2024-11188, GENERIC-standard-pypi-install-pentest, RLUA-2026-00829 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 tomli-dzw 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 tomli-dzw (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tomli-dzw across your stack and pipelines.

Malicious package

tomli-dzwPyPI

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

MAL-2024-11729

Immediate action

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

pip uninstall tomli-dzw

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6f817131e6545bfbdaa6cce0b6a4e0cb4a74e71df2c2e8856113be172ca992bb

d3607336a1196264b6433b324e77707be40051d125299fc1cee2200e4b62bbb9

83d4c8f45a091092f6ceb10a4cb2934e805ac096f6f1c983c49245b5f4d47ee1

89db6f974f1dbda7bc088185e2e6e5729d5e4bf6bbf82fee860218dc9ceb30ca

90fa4d5826e2446bec24aa842b34ff1bd3aea0f2f61abfc2f5c508b5b5039317

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

Campaign

RLMA-2024-11188GENERIC-standard-pypi-install-pentestRLUA-2026-00829

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks tomli-dzw-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