Which versions of telegram-lite-grabber are malicious?

The following PyPI versions of telegram-lite-grabber are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate telegram-lite-grabber if I installed it?

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

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

Yes — telegram-lite-grabber is associated with the 2026-06-telegramlite, IN-MAL-2026-009181 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 telegram-lite-grabber 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 telegram-lite-grabber (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 telegram-lite-grabber across your stack and pipelines.

Malicious package

telegram-lite-grabberPyPI

Malicious code in telegram-lite-grabber (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6051

Immediate action

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

pip uninstall telegram-lite-grabber

What this malware does

Package is named 'telegram-lite-grabber', a name strongly suggestive of a tool intended to harvest Telegram credentials or session data. No concrete malicious behavior was identified in the scanned files, and no install-time or import-time harmful code paths were observed. The name alone, however, warrants human review to assess whether the package distributes attack tooling, contains a payload not surfaced by automated checks, or is otherwise unsuitable for the registry.

Package exfiltrates data from the Telegram application to a remote location, effectively collecting Telegram sessions.

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

Campaign: 2026-06-telegramlite

Reasons (based on the campaign):

target:telegram
files-exfiltration

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

70271d13337a92afafb6d5db770a6d73cd960b6910992013d57ec24388ab8fa8

aad489fe689e441f3237d052bb24702e3178fca26564e662b060c0a8d01fe5f9

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 telegram-lite-grabber (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 telegram-lite-grabber across your stack and pipelines.
If you installed it — respond
telegram-lite-grabber 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 telegram-lite-grabber 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 telegram-lite-grabber 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. telegram-lite-grabber 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

2026-06-telegramliteIN-MAL-2026-009181

References

Credits

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

Detect & block this

O3 blocks telegram-lite-grabber-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