Which versions of inlifegram are malicious?

The following PyPI versions of inlifegram are flagged malicious: 2.1.2.8, 2.1.2.9. Treat any of these as compromised.

How do I remediate inlifegram if I installed it?

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

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

Yes — inlifegram is associated with the 2026-06-inlifegram, IN-MAL-2026-007779, IN-MAL-2026-007780 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 inlifegram 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 inlifegram (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging inlifegram across your stack and pipelines.

Malicious package

inlifegramPyPI

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

MAL-2026-6516

Immediate action

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

pip uninstall inlifegram

What this malware does

InLifeGram distributes a modified copy of the pyrogram Telegram client library and installs it into the top-level pyrogram import namespace, so import pyrogram after installation resolves to this fork. The fork's Client start path has been modified to lazily import a sibling module (from. import app as secret) and, when the authenticated account is a bot (self.me.is_bot), call secret.init(self) wrapped in a bare except Exception: pass. The call hands the fully authenticated client object — containing the bot token, api_id/api_hash, and MTProto auth_key — to undocumented code. The receiving app.py module consists of a single exec(zlib.decompress(base64.b85decode(b'...')).decode()) over an ~11KB opaque blob, with no other functionality and an Indonesian-language header threatening anyone who removes 'credits'. The multi-layer obfuscation (base85 → zlib → exec), the silent invocation on bot authentication, and the bare-except suppression are the canonical shape of a session/token-stealing backdoor. README links a sibling project VLife-Gram by the same author, indicating a family of trojanized forks. Any program that installs InLifeGram and runs a Pyrogram bot will silently surrender its bot session to the hidden payload on every successful login.

The modified version of a Telegram bot library. The obfuscated code, launched when the user starts their own bot application, attaches malicious backdoor commands to the Telegram bot. They allow hardcoded users to execute any commands in the bot's environment.

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

Campaign: 2026-06-inlifegram

Reasons (based on the campaign):

clones-real-package
obfuscation
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat
target:telegram
action-hidden-in-lib-usage
backdoor

Malicious versions

2 flagged

2.1.2.82.1.2.9

Indicators of compromise (SHA-256)

9e2d3483845391abac4b854096ffc1c7767818f9e2b02486d969ee2be0638dc9

3975a0998bf76dddc25f0138b1d4b408bb06304b3203dc1e62e0110b2b56425f

47e605deff389b5280d8c5eac7c01fbdb3f108eade075cb3fd54031b1a03842f

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

Campaign

2026-06-inlifegramIN-MAL-2026-007779IN-MAL-2026-007780

References

Credits

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

Detect & block this

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