Which versions of tgeffect are malicious?

The following PyPI versions of tgeffect are flagged malicious: 1.1.0, 1.1.2, 1.1.3, 1.2.1, 1.3.1, 1.4.1, 1.4.2, 1.4.3, 1.4.4. Treat any of these as compromised.

How do I remediate tgeffect if I installed it?

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

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

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

Malicious package

tgeffectPyPI

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

MAL-2025-191897

Immediate action

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

pip uninstall tgeffect

What this malware does

Importing the module starts obfuscated code which then look for data related to some Telegram clients and attempt to exfiltrate them

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

Campaign: 2025-11-tgeffect

Reasons (based on the campaign):

obfuscation
target:telegram
exfiltration-credentials

Malicious versions

9 flagged

1.1.01.1.21.1.31.2.11.3.11.4.11.4.21.4.31.4.4

Indicators of compromise (SHA-256)

624fb77437544790ca097e5dbddf8b4f9f309bd3f0f5be52f9a97b34a4cdb0f3

e254217ac113edcc1914bdfcda06509137ceed6a7441b3c846653d769335bcaa

9955b619a1f6a19c03fd67e2b7605f97d04dae865c20e77e3d382e065175d5e5

72a3075c57d45010431a0a1fdb7ea7fd5064e54913dbf791811562faa5b46ec8

a360e73139b8ee500ef03e53a4332ee87e9653ce4689ee33ee9cca5270372f89

11284deadc939cb2569f350f0d1d5e571c1dd05a6b12f6b0c549bbc55c109a07

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 tgeffect (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tgeffect across your stack and pipelines.
If you installed it — respond
tgeffect 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 tgeffect 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 tgeffect 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. tgeffect on PyPI has been identified as a malicious package (versions 1.1.0, 1.1.2, 1.1.3, 1.2.1, 1.3.1, 1.4.1, 1.4.2, 1.4.3, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-tgeffectRLMA-2025-06597RLUA-2026-00817

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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