Which versions of mongosooe are malicious?

The following npm versions of mongosooe are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate mongosooe if I installed it?

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

If mongosooe was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is mongosooe part of a known attack campaign?

Yes — mongosooe is associated with the RLMA-2026-06331 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 mongosooe across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mongosooe (version 1.0.1).

Malicious package

mongosooenpm

Advisory published Aug 24, 2026Updated Sep 1, 2026

mongosooe is a confirmed malicious npm package (MAL-2026-15690) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mongosooe (npm)

MAL-2026-15690

Immediate action

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

npm uninstall mongosooe

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

38afaf2b685895d5b3624edd814e189d9dadc3da46b829e367e3e31a45bdf1a3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mongosooe (version 1.0.1).
If you installed it — respond
Remove mongosooe 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 mongosooe was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mongosooe on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-06331

Credits

ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database