Which versions of reverse434343 are malicious?

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

How do I remediate reverse434343 if I installed it?

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

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

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

Malicious package

reverse434343PyPI

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

MAL-2024-11694

Immediate action

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

pip uninstall reverse434343

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)

9f647003c4336c02a6dd642e047113515992496d9fb5aacf1f4caf135e37f572

2e07988de8ac1793c1e2ede3bf518ddd9c0f65e6086a241c968cf3bbf6564f24

9107d563a329f12fdff39bb22f6d6593f6d005d38f9738c2d3a78c94ee368262

bdbb79596d089d99d6a67246fb7f651b54ef2b912c069d02e862250e0257579e

057bd7e0d8383ace96b883d02648c55b6c8abc9f74e4a42b162d10a367a31315

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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