What does the gramapi 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 gramapi are malicious?

The following PyPI versions of gramapi are flagged malicious: 1.0.0, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate gramapi if I installed it?

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

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

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

Malicious package

gramapiPyPI

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

MAL-2025-6513

Immediate action

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

pip uninstall gramapi

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

3 flagged

1.0.01.0.21.0.3

Indicators of compromise (SHA-256)

43e09b4c772dcc6f820f6c1d9afa45843094d16166b4544dd21598a65f9713a0

6c159a05f62456f5baab74fe6eb262de26bc0197e4dc716998acbd314a09c4ff

2c3452393093f1f74c19a9049b50fb9c96e9b31ef8235cf0597eb656e6feb8ea

449b726b8d94155052c2ea096db2129fb5a6d3408dad3992d352fb621d814c60

a930516836313a3b8bacb726092701de52a88eb261565c2eb3e72328c4772aec

edbfccfc49a6f27380df3798cfcf8f53df0abc2f38d85818668e2b765bf380dc

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 gramapi (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gramapi across your stack and pipelines.
If you installed it — respond
gramapi 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 gramapi 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 gramapi 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. gramapi on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-036042025-07-puregramRLUA-2026-00362

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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