What does the my-test-package-2025-xyz malware do?

During installation, the package opens a reverse shell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-05-my-test-package-2025-xyz Reasons (based on the campaign): - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - The package overrides the install command in setup.py to execute malicious code during installation.

Which versions of my-test-package-2025-xyz are malicious?

The following PyPI versions of my-test-package-2025-xyz are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate my-test-package-2025-xyz if I installed it?

my-test-package-2025-xyz 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 my-test-package-2025-xyz — how do I know if it already compromised me?

If my-test-package-2025-xyz 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 my-test-package-2025-xyz part of a known attack campaign?

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

Malicious package

my-test-package-2025-xyzPyPI

Malicious code in my-test-package-2025-xyz (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4837

Immediate action

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

pip uninstall my-test-package-2025-xyz

What this malware does

During installation, the package opens a reverse shell

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

Campaign: 2026-05-my-test-package-2025-xyz

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a2f3ab0a3c7ef9009c99575d9dd051c4a97575435cabf5d3a4c223f53bc47b89

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 my-test-package-2025-xyz (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging my-test-package-2025-xyz across your stack and pipelines.
If you installed it — respond
my-test-package-2025-xyz 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 my-test-package-2025-xyz 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 my-test-package-2025-xyz 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. my-test-package-2025-xyz 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

2026-05-my-test-package-2025-xyz

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks my-test-package-2025-xyz-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