What does the puregram malware do?

The code is automatically starting, calling a Telegram channel with basic info, and waits for remote code to execute Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-puregram Reasons (based on the campaign): - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine. - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Which versions of puregram are malicious?

The following PyPI versions of puregram are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate puregram if I installed it?

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

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

Yes — puregram is associated with the RLMA-2025-03667, 2025-07-puregram, RLUA-2026-00616 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 puregram 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 puregram (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging puregram across your stack and pipelines.

Malicious package

puregramPyPI

Malicious code in puregram (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6569

Immediate action

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

pip uninstall puregram

What this malware does

The code is automatically starting, calling a Telegram channel with basic info, and waits for remote code to execute

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

Campaign: 2025-07-puregram

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

206255c1840073c3aa1356c7df7a8846f213bd5bdc99507ccee0559f8179ff1a

691bad29f8145a268243144df30c43daa620297b46061ba3816354beb3921f46

7bd190edcbb3734a8578c4e0c5dbd9655bc59613d53e67bfd04b3604cf1aa328

4554fbca15157b92eb7788bfa13d4f196db6ef7b5ea09a16f14e727362174b90

ba4d9304a54cef93ef2b61c84830e9cf1d15c295e32314405630b87ec4646a8b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for puregram (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging puregram across your stack and pipelines.
If you installed it — respond
puregram 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 puregram 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 puregram 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. puregram 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

RLMA-2025-036672025-07-puregramRLUA-2026-00616

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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