my-signature
Affected
- Versions:
1.0.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in my-signature (PyPI)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (d4381e88116d48711083bd1e4934b898ce8bc9c347c7d8b5a18762488286d5b2)
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.
Source: kam193 (1b5a4db94700d5c867db98541b7066f27dae28f2d03a806a5d03a00ebce6c52c)
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):
Not rated by the source.
1.0.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0