Which versions of gentorqkkh1 are malicious?

The following PyPI versions of gentorqkkh1 are flagged malicious: 0.1, 0.2. Treat any of these as compromised.

How do I remediate gentorqkkh1 if I installed it?

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

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

Yes — gentorqkkh1 is associated with the RLMA-2024-08313, 2024-07-ronnyfredd-exfiltr-clipboard, RLUA-2026-00350 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 gentorqkkh1 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 gentorqkkh1 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gentorqkkh1 across your stack and pipelines.

Malicious package

gentorqkkh1PyPI

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

MAL-2024-10031

Immediate action

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

pip uninstall gentorqkkh1

What this malware does

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

Campaign: 2024-07-ronnyfredd-exfiltr-clipboard

Reasons (based on the campaign):

peristence-autorun
clipboard-stealing

Malicious versions

2 flagged

0.10.2

Indicators of compromise (SHA-256)

e0f1624d6c01ba26c7fcb7ffb8a659b2aee3dcb6992625961e93d19fd63c74ae

22b8e8b7612572e0413e4cbe22a22183a6a7c767e0f7c00fa4c8c8c45342639f

23c1a7041a4424ef67ce4e182aee3ead70dc15aacd94d20d63b5f7028224d75c

a3d98ba1080ae4e791f828e63715db88a37328e2200a1517b6cdf68232847943

ef6834f0460f440202429853bfd069b72bee75c4e5ae5511ef5542b62efdd543

392b06862ad94c5a7a97b8881155814d2a9ffd05155914905a57f258c06ef8ed

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

Campaign

RLMA-2024-083132024-07-ronnyfredd-exfiltr-clipboardRLUA-2026-00350

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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