Which versions of mw-server-util are malicious?

The following npm versions of mw-server-util are flagged malicious: 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate mw-server-util if I installed it?

mw-server-util establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed mw-server-util — how do I know if it already compromised me?

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

Yes — mw-server-util is associated with the IN-MAL-2026-010724, IN-MAL-2026-010723 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 mw-server-util 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 mw-server-util (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mw-server-util across your stack and pipelines.

Malicious package

mw-server-utilnpm

Malicious code in mw-server-util (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10739

Immediate action

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

npm uninstall mw-server-util

What this malware does

mw-server-util 2.0.1 ships a postinstall hook that runs mw.js, which reads os.hostname() and os.userInfo() and issues an HTTPS GET to a hardcoded Burp Collaborator subdomain gdx35zc4m7hymba6asotmwhd349vxlla.oastify.com, transmitting the installer's hostname, username, package name, and a timestamp on npm install. The destination is an attacker-controlled OAST callback typical of dependency-confusion beacons; the fetch fires automatically as a lifecycle side effect with no relation to any documented package purpose.

Malicious versions

2 flagged

2.0.02.0.1

Indicators of compromise (SHA-256)

1401412848e55e1515db44b1f513ad6e39628f06c24c3b057a08448c9e8ee44c

9827776af0bcdd4df831ab5e5d567d67f18436f256a21b3d528dac3506685261

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mw-server-util (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mw-server-util across your stack and pipelines.
If you installed it — respond
mw-server-util establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If mw-server-util 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 mw-server-util 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. mw-server-util on npm has been identified as a malicious package (versions 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010724IN-MAL-2026-010723

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mw-server-util-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring