Which versions of pullgetsage are malicious?

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

How do I remediate pullgetsage if I installed it?

Remove pullgetsage from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed pullgetsage — how do I know if it already compromised me?

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

Yes — pullgetsage is associated with the IN-MAL-2026-020272 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pullgetsage (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pullgetsage across your stack and pipelines.

Malicious package

pullgetsagePyPI

pullgetsage is a confirmed malicious PyPI package (MAL-2026-16366) that executes malicious code on install (malicious version 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.

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

93b751049f78b324983511537b6c053a0ed080639dd7c447d87494eabc134ba3

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pullgetsage (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pullgetsage across your stack and pipelines.
If you installed it — respond
Remove pullgetsage from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pullgetsage 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 pullgetsage 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. pullgetsage on PyPI has been identified as a malicious package (version 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020272

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pullgetsage-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database