Which versions of dsh-plugin-blender-3d are malicious?

The following npm versions of dsh-plugin-blender-3d are flagged malicious: 0.2.1. Treat any of these as compromised.

How do I remediate dsh-plugin-blender-3d if I installed it?

dsh-plugin-blender-3d 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.

I already installed dsh-plugin-blender-3d — how do I know if it already compromised me?

If dsh-plugin-blender-3d 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.

Is dsh-plugin-blender-3d part of a known attack campaign?

Yes — dsh-plugin-blender-3d is associated with the IN-MAL-2026-021762 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dsh-plugin-blender-3d across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dsh-plugin-blender-3d (version 0.2.1).

Malicious package

dsh-plugin-blender-3dnpm

Advisory published Oct 26, 2026Updated Oct 26, 2026

dsh-plugin-blender-3d is a confirmed malicious npm package (MAL-2026-18321) that steals credentials and exfiltrates sensitive data (malicious version 0.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dsh-plugin-blender-3d (npm)

MAL-2026-18321

Immediate action

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

npm uninstall dsh-plugin-blender-3d

What this malware does

[email protected] is a new release of a DeepSeek Harness plugin for Blender 3D modeling whose only change from 0.2.0 is a postinstall script, sh scripts/miner.sh, that runs on npm install. The script downloads a gzip carrier from amplify-gursha-dev-121835-deployment.s3.amazonaws.com to /tmp/.smh; as root or with passwordless sudo it runs the carrier's installer (sh /tmp/.smi agent), which installs an XMRig miner plus two helper daemons under random system-component names and persists them as systemd units or @reboot cron entries, and otherwise it extracts the bundled XMRig binary to ~/.local/lib/<random name>/ and mines Monero to networkservicesupp.flashhub.net:8443 over TLS with a hardcoded wallet. The npm account walknpm published the same scripts/miner.sh in @walknpm/[email protected] within 27 seconds of this version on 2026-10-26, and it is byte-identical to the one in @sudobility/testomniac_client (MAL-2026-18129).

dsh-plugin-blender-3d declares a postinstall script (sh scripts/miner.sh) that fires automatically on npm install. The script downloads a gzip payload from https://amplify-gursha-dev-121835-deployment.s3.amazonaws.com (authenticated via a hardcoded AWS access key <redacted> and presigned signature) to /tmp/.smh, decompresses it to /tmp/.smi, and executes it. When root or passwordless sudo is available (sudo -n), the script runs the decompressed payload as sh /tmp/.smi agent under nohup; in-file comments describe this branch as a 'full persistent agent install' that renames binaries to system-component-like stealth names and installs cron plus relay/tor persistence. In the non-root fallback the script extracts a bundled XMRig miner, writes a pool configuration to $HOME/.sysmond.json targeting networkservicesupp.flashhub.net:8443, stages the miner under $HOME/.local/lib/<stealth-name>/, and launches it via nohup with an idempotency lock. The attacker gains CPU resources on the installer host, root-level code execution where sudo is passwordless, and persistent backdoor access with a tor/relay channel.

The OpenSSF Package Analysis project identified 'dsh-plugin-blender-3d' @ 0.2.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.2.1

Indicators of compromise (SHA-256)

ae55a6a112dc0b823afa1c7c0217871c1c19b5d0b77fde2a8ec29d4b26a9549b

08bd399ddec36950a4cb3c82cb8460e95cde40441f464fbff1d215f6a7f13937

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dsh-plugin-blender-3d (version 0.2.1).
If you installed it — respond
dsh-plugin-blender-3d 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.
Did it already run?
If dsh-plugin-blender-3d 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-plugin-blender-3d on npm has been identified as a malicious package (version 0.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021762

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder
OpenSSF: Package Analysis · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database