# MAL-2026-18130: Malicious code in @sudobility/wildduck_client (npm)


- **Type:** Malicious package
- **Package:** `@sudobility/wildduck_client` (npm)
- **Published:** 21 Oct 2026
- **Also known as:** GHSA-5ff7-5w72-hm63

## What is MAL-2026-18130?

MAL-2026-18130 is a malicious package in @sudobility/wildduck_client, published on 21 Oct 2026. 

### Official description

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.

## What should I do about MAL-2026-18130?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-18130 is a malicious package: @sudobility/wildduck_client (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-18130/ (Markdown: https://insights.sbomify.com/MAL-2026-18130/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-18130

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-18130/
Summaries are generated and may contain mistakes; the official description above is the record.