NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

my-signaturePyPI

Advisory published Updated

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

Malicious code in my-signature (PyPI)

MAL-2026-19953
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall my-signature

What this malware does

my-signature 1.0.0 is advertised as a document integrity utility but contains import-time code (core.py, reached from init.py) that opens a TCP socket to ahqbb-13-205-45-209.run.pinggy-free.link:43017 (a Pinggy tunnel fronting 13.205.45.209), duplicates stdin/stdout/stderr onto that socket, and spawns /bin/sh via pty.spawn. Any import my_signature hands an interactive shell on the installer's host to the operator of that tunnel endpoint, with full privileges of the Python process. The behavior is unrelated to the package's stated purpose and fires automatically on import with no user interaction.

During import, the package attempts to start a reverse shell.

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

Campaign: 2026-11-my-poc-sandbox

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

1b5a4db94700d5c867db98541b7066f27dae28f2d03a806a5d03a00ebce6c52c
d4381e88116d48711083bd1e4934b898ce8bc9c347c7d8b5a18762488286d5b2

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for my-signature (version 1.0.0).

  2. If you installed it — respond

    my-signature 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.

  3. Did it already run?

    If my-signature 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. my-signature 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

2026-11-my-poc-sandboxIN-MAL-2026-022814

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks my-signature-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

my-signature (PyPI) malicious package — MAL-2026-19953 | O3 Security