Which versions of dt-validator are malicious?

The following PyPI versions of dt-validator are flagged malicious: 0.3.0. Treat any of these as compromised.

How do I remediate dt-validator if I installed it?

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

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

Yes — dt-validator is associated with the 2026-06-dt-validator 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 dt-validator 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 dt-validator (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dt-validator across your stack and pipelines.

Malicious package

dt-validatorPyPI

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

MAL-2026-6728

Immediate action

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

pip uninstall dt-validator

What this malware does

Code contains a function to execute remote code, which at the time of analysis was extracting the "auth_user" table from Django DB. The remote code execution is partially documented and disguised with multiple warnings, but a) the 'convenience function' uses a hardcoded endpoint and loads results to the global namespace, b) the warnings are silenced by default.

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

Campaign: 2026-06-dt-validator

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
action-hidden-in-lib-usage

Malicious versions

1 flagged

0.3.0

Indicators of compromise (SHA-256)

0fc0256380d811cdce05ffa9c3644a5f7e4ebd6f7acfce0f955935b42449b17a

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

Campaign

2026-06-dt-validator

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks dt-validator-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