Which versions of MFQ-Private-Encoder are malicious?

The following PyPI versions of MFQ-Private-Encoder are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate MFQ-Private-Encoder if I installed it?

Remove MFQ-Private-Encoder from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed MFQ-Private-Encoder — how do I know if it already compromised me?

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

Yes — MFQ-Private-Encoder is associated with the IN-MAL-2026-010793 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 MFQ-Private-Encoder 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 MFQ-Private-Encoder (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 MFQ-Private-Encoder across your stack and pipelines.

Malicious package

MFQ-Private-EncoderPyPI

Malicious code in mfq-private-encoder (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-10758

Immediate action

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

pip uninstall MFQ-Private-Encoder

What this malware does

The package advertises a Python source-code encoder but has no local codec. The encode_file function and public encode() API read the user-supplied Python file and POST its full contents to a hardcoded Cloudflare Worker at https://mapping-worker.email-ecf.workers.dev/encode using a hardcoded API key, routing all caller source to an author-controlled endpoint. The mfq-encode CLI emits output scripts of the form import mfqencoder; encoded_string='...'; exec(mfqencoder.decode(encoded_string)), where mfqencoder.decode POSTs to https://mapping-worker.email-ecf.workers.dev/decode and the response bytes are passed directly to exec() with no signature or hash verification. Any downstream execution of an 'encoded' script runs whatever the author's worker returns at that moment. A 64-character hex API key for the author's worker is also hardcoded in __init__.py, encoder.py, and decoder.py.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6f2c0f78a3c5677481645e05e125f32273435610a1208a17ca4f852cb7f56b0e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for MFQ-Private-Encoder (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 MFQ-Private-Encoder across your stack and pipelines.
If you installed it — respond
Remove MFQ-Private-Encoder from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If MFQ-Private-Encoder 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 MFQ-Private-Encoder 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. MFQ-Private-Encoder 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

IN-MAL-2026-010793

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks MFQ-Private-Encoder-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring