Which versions of moonbit-locale-compat are malicious?

The following PyPI versions of moonbit-locale-compat are flagged malicious: 0.2.1, 0.2.3, 0.2.4. Treat any of these as compromised.

How do I remediate moonbit-locale-compat if I installed it?

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

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

Yes — moonbit-locale-compat is associated with the 2026-04-moonbit-locale-compat 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 moonbit-locale-compat 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 moonbit-locale-compat (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging moonbit-locale-compat across your stack and pipelines.

Malicious package

moonbit-locale-compatPyPI

Malicious code in moonbit-locale-compat (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2945

Immediate action

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

pip uninstall moonbit-locale-compat

What this malware does

Campaign includes a chain of dependencies that finally exfiltrate sensitive environment variables to a hardcoded GitHub repository as exfiltration target, and in specific environments also start a reverse shell. It appears to be targeting specifically one GitHub project, where the front-end package was included in a PR.

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

Campaign: 2026-04-moonbit-locale-compat

Reasons (based on the campaign):

The malicious code is intentionally included in a dependency of the package
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
exfiltration-env-variables

Malicious versions

3 flagged

0.2.10.2.30.2.4

Indicators of compromise (SHA-256)

d42bb32adb1fb5f388368b9e4ab382bfbc8cd7f62dab4c70a8563a448ce9c2af

d78a796f48577a4aacd59312b19e5aba799631ce77b36bebb5c64c4e523cd9b8

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

Campaign

2026-04-moonbit-locale-compat

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks moonbit-locale-compat-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