Which versions of reverse4343 are malicious?

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

How do I remediate reverse4343 if I installed it?

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

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

Yes — reverse4343 is associated with the RLMA-2024-11151, 2024-11-predic, RLUA-2026-00720 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 reverse4343 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 reverse4343 (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 reverse4343 across your stack and pipelines.

Malicious package

reverse4343PyPI

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

MAL-2024-11693

Immediate action

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

pip uninstall reverse4343

What this malware does

The package contains only a reverse shell started on installation

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

Campaign: 2024-11-predic

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f811cb4ba1e6b240cc810088eeeba089ea364fe238ac2a32beac37d8e0ea8ac2

ab1b4cee06c50bb33c1321dbec71490ccb29b7f8fa8f10e6b0c8ca510dd788e6

a90c21a3dc6b4091f1ccd6f17c99b1ec955954d2b78e93029e63c33f12ed3c7d

922c347fff4ff195d0fe835451e5084fcaded25f81ac2db2bb2c9899956180c3

cbcd627e081ca636ac4e4038da82d889c09335b0366b1ea824f6997213272654

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 reverse4343 (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 reverse4343 across your stack and pipelines.
If you installed it — respond
reverse4343 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 reverse4343 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 reverse4343 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. reverse4343 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-111512024-11-predicRLUA-2026-00720

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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