Which versions of sghsuzeghuisehguihdrhffdhfdh are malicious?

The following PyPI versions of sghsuzeghuisehguihdrhffdhfdh are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate sghsuzeghuisehguihdrhffdhfdh if I installed it?

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

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

Yes — sghsuzeghuisehguihdrhffdhfdh is associated with the RLMA-2024-09260, funcaptcha-ru 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 sghsuzeghuisehguihdrhffdhfdh 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 sghsuzeghuisehguihdrhffdhfdh (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 sghsuzeghuisehguihdrhffdhfdh across your stack and pipelines.

Malicious package

sghsuzeghuisehguihdrhffdhfdhPyPI

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

MAL-2024-10160

Immediate action

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

pip uninstall sghsuzeghuisehguihdrhffdhfdh

What this malware does

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

Campaign: funcaptcha-ru

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

de7e85191375c04b4569db0c6900c476e8d872b305c8c2076d2685b8daf8d39e

a6f71daa0a90b6d5540221936884a22f18cc56973524283af4af298e2054ddb5

ad9c9ad0fe77fff4c0f86068a374a6abae12b08c23d470837f3a4a8df01648c2

08511f2dc1194a12f6269af2397d0b36c80517beb17ba286de59a264ee1aedf4

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

RLMA-2024-09260funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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