Which versions of gentorqkkh are malicious?

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

How do I remediate gentorqkkh if I installed it?

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

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

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

Malicious package

gentorqkkhPyPI

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

MAL-2024-10030

Immediate action

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

pip uninstall gentorqkkh

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

1 flagged

0.1

Indicators of compromise (SHA-256)

fbe35bc7d1f9528f87bfa4d945b86677b76a63abd39adbfc38b2321603ef84a6

b093b86c30b796f3f748d9dfb6205c6796c871dad58abea9da6b47da31f4ce5f

d6d9d057c596541a3467728f7e2fc38dd60f4ad166c64ef77db6edef26247277

619c1c18a2867ae512d4b324e47b62ad53ca182c539ec275233fce03889a896c

f8054227a393db3420d4b72c7be8029fab1b6fc0764c60707a8457e886fdc8cd

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

Campaign

RLMA-2024-083122024-07-ronnyfredd-exfiltr-clipboardRLUA-2026-00349

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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