Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

dsh-volcengine-providernpm

Advisory published Updated

dsh-volcengine-provider is a confirmed malicious npm package (MAL-2026-18374) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.5, 0.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dsh-volcengine-provider (npm)

MAL-2026-18374
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dsh-volcengine-provider

What this malware does

Analysis of dsh-volcengine-provider 0.2.8 produced no evidence of installer-side attack behavior: no install-time lifecycle scripts fetching or executing remote code, no credential or environment-variable harvesting, no silent relay of caller data to attacker-controlled destinations, no backdoor/reverse-shell mechanism, and no self-propagation or dropper patterns across the 45 files inspected.

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.

Malicious versions

2 flagged
0.2.50.2.8

Indicators of compromise (SHA-256)

4397974f8ab42cc73f71b43f0551a35e8be7a8cb6c971dcdd22608a9698425d5
10d3dafa3da7dea0655bf429e4da622be99e705dd12cbfffb381a0f987f6b550
9016aff24da4e5bf86715a950b05bb994fddb7d933f670e071de0e70a35830c5

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for dsh-volcengine-provider (2 malicious versions).

  2. If you installed it — respond

    dsh-volcengine-provider is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If dsh-volcengine-provider 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. dsh-volcengine-provider on npm has been identified as a malicious package (versions 0.2.5, 0.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8hr2-m7vq-fhpgIN-MAL-2026-022174IN-MAL-2026-022202

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dsh-volcengine-provider-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

dsh-volcengine-provider (npm) malicious package — MAL-2026-18374 | O3 Security