Which versions of modeflow are malicious?

The following PyPI versions of modeflow are flagged malicious: 0.0.1, 0.0.2, 0.1.0. Treat any of these as compromised.

How do I remediate modeflow if I installed it?

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

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

Yes — modeflow is associated with the RLMA-2024-08526, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00531 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 modeflow 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 modeflow (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging modeflow across your stack and pipelines.

Malicious package

modeflowPyPI

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

MAL-2024-10047

Immediate action

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

pip uninstall modeflow

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

3 flagged

0.0.10.0.20.1.0

Indicators of compromise (SHA-256)

7f9a0e5bdbc0853bc44630e61ee30b7e4d5a1cb22c9dde772f8e4e2e63838075

f32afbb6d10e053d30a39dc3fc850f2b0b39c0b4b48bfc4200ccf99e25bb90ce

9499d9dbc7c99f3ef3720a91b51ebfe6e0eac051ca6110233f16a61c762c2b8d

871545024537348c08c966add8807336da69727a340d371d4d9819a3f4f16a91

29facc4b9bd6ebc26a51a372cc77fc2af62452f8f0056c11af96b9ef2468a375

1b9a0ba0750e838bd5cccaf7f175d961c09d3ce0e6fc7ad91d440e14184d31e8

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

Campaign

RLMA-2024-085262024-08-embeds-RealtekHDAudioManagerRLUA-2026-00531

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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