idnnaPyPI
idnna is a confirmed malicious PyPI package (MAL-2026-13488) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.1, 0.1.2, 0.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in idnna (PyPI)
What this malware does
The package publishes under a name that closely resembles the widely-used idna package and advertises itself as 'HTTP client utilities', but the only importable module is djangoo containing a trivial hello() function. setup.py registers a custom install cmdclass (LinuxInstall) whose post-install step base64-decodes a hidden Python payload stored in _HOOK_B64 and executes it via exec(compile(...)). On Linux, the decoded payload uses urlretrieve to download an opaque binary named something from https://github.com/totti2188/8gp1Q7iZD3h4VW/releases/download/v1.3A/something — an unrelated personal GitHub account whose repository has no connection to the package's stated purpose — chmods it to 0o755, and spawns it detached via Popen. The download destination is not publisher-matched, the fetched artifact is unpinned by hash, and the payload is obfuscated to evade casual review. This fires automatically on pip install of the sdist.
Package imitates name of a popula library. During installation, obfuscated code downloads a malicious executable and starts it. It then exfiltrates at least cryptocurrency wallet data, probably more.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-flasq
Reasons (based on the campaign):
-
typosquatting
-
The package overrides the install command in setup.py to execute malicious code during installation.
-
exfiltration-generic
-
Downloads and executes a remote executable.
-
obfuscation
-
exfiltration-crypto
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for idnna (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging idnna across your stack and pipelines.
If you installed it — respond
idnna 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 idnna 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 idnna 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks idnna-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.