What does the dhgshop malware do?

The package dhgshop was found to contain malicious code. The OpenSSF Package Analysis project identified 'dhgshop' @ 9.0.10 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of dhgshop are malicious?

The following npm versions of dhgshop are flagged malicious: 9.0.9, 9.0.10. Treat any of these as compromised.

How do I remediate dhgshop if I installed it?

Remove dhgshop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dhgshop — how do I know if it already compromised me?

If dhgshop was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find dhgshop across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dhgshop (2 malicious versions).

Malicious package

dhgshopnpm

Advisory published Jan 29, 2026Updated Feb 2, 2026

dhgshop is a confirmed malicious npm package (MAL-2026-605) that executes malicious code on install (malicious versions 9.0.9, 9.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhgshop (npm)

MAL-2026-605

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dhgshop

What this malware does

The package dhgshop was found to contain malicious code.

The OpenSSF Package Analysis project identified 'dhgshop' @ 9.0.10 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

9.0.99.0.10

Indicators of compromise (SHA-256)

194b5b6f2e47a1b70386a65d094c4b7d07a4fad392f36512b21542203c931dba

4eb94cb85796b5ec461434b25c82e9e69ff87228fb007a8b154472ae5f49627b

dcf692c43737b2f7360ab017ae983283e98b2d2591a90a3efff90685a95d2632

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhgshop (2 malicious versions).
If you installed it — respond
Remove dhgshop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dhgshop was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dhgshop on npm has been identified as a malicious package (versions 9.0.9, 9.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks dhgshop-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database