Which versions of @sudobility/wildduck_client are malicious?

The following npm versions of @sudobility/wildduck_client are flagged malicious: 2.3.102. Treat any of these as compromised.

How do I remediate @sudobility/wildduck_client if I installed it?

@sudobility/wildduck_client 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 @sudobility/wildduck_client — how do I know if it already compromised me?

If @sudobility/wildduck_client 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 @sudobility/wildduck_client part of a known attack campaign?

Yes — @sudobility/wildduck_client is associated with the IN-MAL-2026-021560, GHSA-5ff7-5w72-hm63 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 @sudobility/wildduck_client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sudobility/wildduck_client (version 2.3.102).

Malicious package

@sudobility/wildduck_clientnpm

Advisory published Oct 21, 2026Updated Oct 22, 2026

@sudobility/wildduck_client is a confirmed malicious npm package (MAL-2026-18130) that steals credentials and exfiltrates sensitive data (malicious version 2.3.102). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sudobility/wildduck_client (npm)

MAL-2026-18130

Immediate action

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

npm uninstall @sudobility/wildduck_client

What this malware does

The package declares a postinstall hook that executes scripts/miner.sh on npm install. The script fetches a gzipped payload from a presigned AWS S3 URL (amplify-gursha-dev-121835-deployment.s3.amazonaws.com) using a hardcoded AWSAccessKeyId (<redacted>), writes it to /tmp/.smh, decompresses to /tmp/.smi, and executes it. When root or passwordless sudo is available, it launches sh /tmp/.smi agent with elevated privileges to install a persistent agent (cron plus relay/tor) under stealth system-component process names. Without root, it extracts an embedded base64/tar XMRig binary, writes a mining configuration to ~/.sysmond.json pointing at the pool networkservicesupp.flashhub.net:8443 with a hardcoded wallet, copies the miner to ~/.local/lib/<stealth-name>/<stealth-name>, and launches it via nohup. The package is published under a WildDuck email-client identity that does not correspond to the behavior shipped in the install script.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.3.102

Indicators of compromise (SHA-256)

a4524dc6ef26909f4ddfaf83eae1ec13495a5b2aef57375c0a8d8ad4c0609637

02f525da4c4c8ee5f075a0331435ead2dd17b0ce972b32506ec7dafbf358867b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @sudobility/wildduck_client (version 2.3.102).
If you installed it — respond
@sudobility/wildduck_client 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 @sudobility/wildduck_client 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. @sudobility/wildduck_client on npm has been identified as a malicious package (version 2.3.102 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021560GHSA-5ff7-5w72-hm63

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sudobility/wildduck_client-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

Explore

All malware advisories How O3 detects malware Vulnerability database