What does the farooq4321 malware do?

Code in setup.py attempts to call a webhook, but most importantly to execute a revshell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-02-farooq4321 Reasons (based on the campaign): - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - The package overrides the install command in setup.py to execute malicious code during installation.

Which versions of farooq4321 are malicious?

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

How do I remediate farooq4321 if I installed it?

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

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

Yes — farooq4321 is associated with the RLMA-2025-01216, 2025-02-farooq4321, RLUA-2026-00315 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 farooq4321 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 farooq4321 (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 farooq4321 across your stack and pipelines.

Malicious package

farooq4321PyPI

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

MAL-2025-1975

Immediate action

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

pip uninstall farooq4321

What this malware does

Code in setup.py attempts to call a webhook, but most importantly to execute a revshell

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

Campaign: 2025-02-farooq4321

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5e73139e6b9c692a8fe69bf7bd6afacf2d15c854fad546a90f4e18d04005c50c

ceb936fd2fc63bff68bca177780c745be2347bf7b1175b52f68c58ab81e3007d

165ce280a6d073eebbba054677a6c80307c8353b31e41732ba1ffc1f8a020aa4

43e9a968d119c0ae87cad73f5ffae0b3acee0fd7475f0ee3205ead682390dcd7

8440182ffbe72f527d4f14fd778e5d27f9151c2a33847eba9800889e84ebc416

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 farooq4321 (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 farooq4321 across your stack and pipelines.
If you installed it — respond
farooq4321 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 farooq4321 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 farooq4321 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. farooq4321 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-2025-012162025-02-farooq4321RLUA-2026-00315

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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