Which versions of bytedmemfdd345 are malicious?

The following PyPI versions of bytedmemfdd345 are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate bytedmemfdd345 if I installed it?

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

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

Yes — bytedmemfdd345 is associated with the RLMA-2025-02559, 2025-04-byted-torch-monitor, RLUA-2026-00170 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 bytedmemfdd345 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 bytedmemfdd345 (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytedmemfdd345 across your stack and pipelines.

Malicious package

bytedmemfdd345PyPI

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

MAL-2025-4208

Immediate action

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

pip uninstall bytedmemfdd345

What this malware does

During installation, a website with the current working dir is being called. It looks like something between spam and pentest as the website is most probably not in the control of the uploader. 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: 2025-04-byted-torch-monitor

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.

Malicious versions

1 flagged

0.2

Indicators of compromise (SHA-256)

2d3b30c7efcde00f6760e0fbf892a3607f5fe6689ca25712e79116bc2acd39a7

718afb775d6facebb6f9d228275af5188a6a8d5438846fcb32acee65c8d68c77

19705d4db8178a4b1dd1282ded6d73256dc10b22125280c241524ec3e9e274af

966aa24ad3dff357d83bb59e3dec38022c87f5e2a6528368f01fa69d9f11c3df

3dd1ed480803ea08585f74d47b2f8e8151f33c862379c3b7bdeafc7936e8f2a2

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 bytedmemfdd345 (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytedmemfdd345 across your stack and pipelines.
If you installed it — respond
bytedmemfdd345 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 bytedmemfdd345 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 bytedmemfdd345 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. bytedmemfdd345 on PyPI has been identified as a malicious package (version 0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025592025-04-byted-torch-monitorRLUA-2026-00170

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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