Which versions of testing1345 are malicious?

The following PyPI versions of testing1345 are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate testing1345 if I installed it?

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

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

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

Search your lockfiles and build artifacts for testing1345 (version 0.1.0).

Malicious package

testing1345PyPI

Advisory published Nov 13, 2026Updated Nov 13, 2026

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

Malicious code in testing1345 (PyPI)

MAL-2026-19247

Immediate action

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

pip uninstall testing1345

What this malware does

During installation, the package downloads and executes a script from a remote location. The server delivers different payload versions, some of them being benign, and others containing next-stage installation. The final payload is a RAT.

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

Campaign: 2026-11-testing1345

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
The package overrides the install command in setup.py to execute malicious code during installation.
rat

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

15bab830cd8343859ac220ef87e821719169a4e2ccb50da37032d97ef02c27dd

48d6feb6315919cb99e4b19a9f8342a8fd929affcb24f6e46b7c53224534461a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for testing1345 (version 0.1.0).
If you installed it — respond
testing1345 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 testing1345 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. testing1345 on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-11-testing1345

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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