Malicious code in dsh-native (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7c9c9d92d65945abec57f269176d5080795ae9d832ab6f95525756cd508951bb) The package's index.js contains occurrences of the token 'ping' across several lines (19, 526, 656, 690, 980), which triggered a pattern rule for network/command co-occurrence. No concrete installer-harm behavior is identifiable from this signal alone: there is no named attacker-controlled destination, no read of installer secrets (home-directory credential paths, environment scraping), no install-time or import-time fetch-and-execute, no lifecycle script coupling, and no silent-relay of caller-supplied data. The matched token is consistent with ordinary network diagnostics, latency measurement, or string references rather than a specific exfiltration or C2 path. ## Source: ghsa-malware (6071592c29a573472ed3b8b3be61cb6f0a4c1801ff1ffd3f730f6e14d9e9000b) 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.

Source published

26 Oct 2026 02:17:08 UTC

Source modified

29 Oct 2026 14:30:40 UTC

Observed here

29 Oct 2026 15:12:22 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.