Which versions of dependency133434fr43437 are malicious?

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

How do I remediate dependency133434fr43437 if I installed it?

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

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

Yes — dependency133434fr43437 is associated with the RLMA-2025-00453, GENERIC-standard-pypi-install-pentest, RLUA-2026-00257 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 dependency133434fr43437 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 dependency133434fr43437 (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 dependency133434fr43437 across your stack and pipelines.

Malicious package

dependency133434fr43437PyPI

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

MAL-2025-914

Immediate action

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

pip uninstall dependency133434fr43437

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
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)

07da80374027abc9cc556dc5038be29e1cbc651570bb91dd04de976a38b2896d

1ad8be7ae9e96193c39c3604d1f736a0d9da6625438275849c54edea43245a44

9cc68a9f63c26e040592558af43d4f7ef6369cbf6623c8f2558fc490acfabb73

42b314e2110fe1fee171e7a9f6b6a6aceb60541e66fa73c0165fa8a68da9e28d

411aa4b74736a65e1c951e3f62f08692a2668c24711ff5066e176e6cea1fa085

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 dependency133434fr43437 (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 dependency133434fr43437 across your stack and pipelines.
If you installed it — respond
dependency133434fr43437 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 dependency133434fr43437 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 dependency133434fr43437 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. dependency133434fr43437 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-00453GENERIC-standard-pypi-install-pentestRLUA-2026-00257

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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