MalwarePublished 26 Oct 2026Updated 29 Oct 2026

dsh-native (npm) · Malicious Code

Affects dsh-nativeSource GCVE Database

Malicious package : remove dsh-native and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 18:22 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18315

What to do

Remove dsh-native from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmdsh-native	Affected =1.4.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'dsh-native' version 1.4.1 contains malicious code that can fully compromise any computer on which it is installed or running. The compromise potentially exposes all stored secrets and keys, which should be rotated immediately from a different machine. Removal of the package alone does not guarantee elimination of all malicious software introduced by its installation.

Impact

Full system compromise on any computer with the package installed or running. All secrets and keys stored on the compromised system are at risk and must be rotated immediately from a different, secure machine. The attacker may maintain persistent access beyond removal of the package.

Defensive guidance

Immediately remove the 'dsh-native' package version 1.4.1 from affected systems. Rotate all secrets and keys stored on compromised machines from a separate, secure computer. Conduct a thorough investigation and remediation for potential persistent malicious software beyond the package itself.

Summary

The 'dsh-native' npm package version 1.4.1 was found to contain malicious code. Although initial automated analysis detected network-related tokens such as 'ping' without clear installer-harm behavior, further assessment indicates that any system with this package installed should be considered fully compromised. The malicious code may grant an attacker full control over the affected system, necessitating immediate secret and key rotation and package removal. However, removal may not fully eradicate the compromise due to potential persistence of other malicious components.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 18:22 UTC

Technical details

References

Community reviews