supply chain event / NVI-00008658 / Revision 1
Malicious code in @sudobility/wildduck_client (npm)
GitHub lists this malware advisory for @sudobility/wildduck_client. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
@sudobility/wildduck_client
source listed= 2.3.102
## Source: amazon-inspector (a4524dc6ef26909f4ddfaf83eae1ec13495a5b2aef57375c0a8d8ad4c0609637) 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 (), 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//, 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. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/e4cf5c2f85ea1249db64cc275e6f1cfef
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-vhv8-cmrm-5fpr ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.