What does the mongland malware do?

Importing the module starts an infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-11-mescouilles Reasons (based on the campaign): - infostealer - infostealer:kiwi - infostealer:cstealer - exfiltration-generic - exfiltration-browser-data - exfiltration-credentials - files-exfiltration - The package contains code to detect if it is running in a sandbox environment.

Which versions of mongland are malicious?

The following PyPI versions of mongland are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate mongland if I installed it?

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

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

Yes — mongland is associated with the 2025-11-mescouilles, RLMA-2025-06577, RLUA-2026-00533 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 mongland 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 mongland (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mongland across your stack and pipelines.

Malicious package

monglandPyPI

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

MAL-2025-191794

Immediate action

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

pip uninstall mongland

What this malware does

Importing the module starts an infostealer

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

Campaign: 2025-11-mescouilles

Reasons (based on the campaign):

infostealer
infostealer:kiwi
infostealer:cstealer
exfiltration-generic
exfiltration-browser-data
exfiltration-credentials
files-exfiltration
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8306945289f884c7d56049fc97db716e2affec48cad1d6981a8f06f04f3554de

a003c7277ab04d5aec30eaa72b0f28b25c7534e6b036c381142300b3ac0bde9f

568acdec5229df37b2bd076481462cf97f404b1839c6f3401669ce197c846e5d

4232275caeafe94ced160806250c5a8faf9f40f088f46571fc299a157ff141c1

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

Campaign

2025-11-mescouillesRLMA-2025-06577RLUA-2026-00533

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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