Which versions of nflx-metaflow are malicious?

The following PyPI versions of nflx-metaflow are flagged malicious: 1.0.0, 1.0.2. Treat any of these as compromised.

How do I remediate nflx-metaflow if I installed it?

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

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

Yes — nflx-metaflow is associated with the RLMA-2025-01225, 2025-02-pxz, RLUA-2026-00557, RLUA-2026-02075 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 nflx-metaflow 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 nflx-metaflow (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nflx-metaflow across your stack and pipelines.

Malicious package

nflx-metaflowPyPI

Malicious code in nflx-metaflow (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-1984

Immediate action

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

pip uninstall nflx-metaflow

What this malware does

Packages are designed to collect basic info about the user when importing them, and have no other purpose. While they claim to do so, some packages from the same uploader use confusing names, clearly suggesting the intention to harvest data from unintentional installations.

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-02-pxz

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.
typosquatting

Malicious versions

2 flagged

1.0.01.0.2

Indicators of compromise (SHA-256)

93230d2f520c9253b2f966d8fe3e8bf0a915dfa22c66d1ae8d80e7e62d8ddc62

a1de66c2c69e749708b919f50ac31dc4ffe5912a35a828aba3e9de9629070a16

1d317c47382e978342b2098c06b1d0ff46acfefdc5a5ed6ce2b531b1f5b24fe4

0dc831f89dd54ed3a6feb918738f6168129be0333c39ca1ac638e38707c14a58

7d4b82ebf73c69d5fcd39308c2b3456b9382214cc0028c2a048aa9d696163ed4

a03fc9b5a9913f50c2d658d6b3d3cc74cd24ede1b19a75813fd7d666fbaa2fea

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

Campaign

RLMA-2025-012252025-02-pxzRLUA-2026-00557RLUA-2026-02075

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks nflx-metaflow-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