Which versions of pullgetsage are malicious?

The following PyPI versions of pullgetsage are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate pullgetsage if I installed it?

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

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

Yes — pullgetsage is associated with the IN-MAL-2026-020272, 2026-09-aiosendletter, IN-MAL-2026-020465, IN-MAL-2026-020466 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 pullgetsage across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pullgetsage (3 malicious versions).

Malicious package

pullgetsagePyPI

Advisory published Sep 21, 2026Updated Sep 23, 2026

pullgetsage is a confirmed malicious PyPI package (MAL-2026-16366) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pullgetsage (PyPI)

MAL-2026-16366

Immediate action

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

pip uninstall pullgetsage

What this malware does

On import, init.py archives the installer's Telegram Desktop tdata directory (%APPDATA%/Telegram Desktop/tdata) into a zip named 'aiosendletter_logs' and POSTs it to a hardcoded Cloudflare Workers endpoint at https://red-poetry-6b6f.martinmcflywork.workers.dev/. The tdata directory holds Telegram session keys; uploading it enables full account takeover of the installer's Telegram account. The behavior is disguised with misleading identifiers ('aiosendletter_logs', 'aioletter initialized') and empty except-block prints that silently swallow errors, and the stated package purpose ('a library filled with books') is unrelated to Telegram.

Package hides code to exfiltrate files. Most releases target unclear files, but some reveal the goal to exfiltrate sensitive Telegram data.

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

Campaign: 2026-09-aiosendletter

Reasons (based on the campaign):

files-exfiltration
target:telegram

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

93b751049f78b324983511537b6c053a0ed080639dd7c447d87494eabc134ba3

5a4369fbf36c4c2a54c7555febeaf8fda122d33a7ba9b9d11e77031849f5c7d8

a8681b3c6d6950321d2104c5f744bdcb237baaa3b855a1f40ecf61aac3f59a7b

87b03140924cb064b6229747c68b2b2dfc34c09a2790af5bbe09946009d7c3e4

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-0202722026-09-aiosendletterIN-MAL-2026-020465IN-MAL-2026-020466

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · analyst

Detect & block this

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