MalwarePublished 23 Sep 2026

caphsmgiwy (npm) · Malicious Code

Affects caphsmgiwySource GCVE Database

Malicious package : remove caphsmgiwy and rotate any secrets on hosts that installed it.

Data as of 23 Sep 2026, 06:22 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-16447

What to do

Remove caphsmgiwy 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
npmcaphsmgiwy	Affected =1.0.1 =1.0.0	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 'caphsmgiwy' versions 1.0.0 and 1.0.1 contain malicious code or depend on a malicious package. Installing or running this package can lead to a full compromise of the affected computer, risking exposure of all stored secrets and keys. Immediate removal of the package and rotation of all secrets from a different, secure computer is strongly advised.

Impact

Systems with 'caphsmgiwy' versions 1.0.0 or 1.0.1 installed are at risk of full compromise, including unauthorized access and control by attackers. All secrets and keys stored on the compromised system may be exposed and should be considered compromised. The presence of this package can lead to severe security breaches.

Defensive guidance

Remove the 'caphsmgiwy' package immediately from all affected systems. Rotate all secrets and keys that were stored on the compromised systems using a different, secure computer. Due to the risk of persistent malicious code, consider full system remediation or reimaging to ensure complete removal of the threat.

Summary

The npm package 'caphsmgiwy' versions 1.0.0 and 1.0.1 have been identified as containing malicious code or relying on a malicious dependency. According to Amazon Inspector and GHSA malware sources, 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/key rotation and package removal. However, removal alone may not eliminate all malicious components due to potential persistence mechanisms.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Sep 2026, 06:22 UTC

Technical details

References

Community reviews