GHSA-hw9g-f63g-4c8x: Malicious code in dsh-plugin-blender-3d (npm)

Published Oct 26, 2026
·
Updated

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.

Affected Software

1 affected component
npm/dsh-plugin-blender-3d=0.2.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove npm/dsh-plugin-blender-3d from your environment.

    Remove dsh-plugin-blender-3d, including version 0.2.1.

  2. Operational

    Immediately rotate all secrets and keys stored on any computer that had this package installed or running, using a different computer.

Event History

Oct 26, 2026
Advisory Published
via OSV·12:55 AM
Data Sourced
via OSV·12:55 AM
DescriptionAffected Software
Oct 28, 2026
Advisory Published
via GitHub·06:09 PM
Data Sourced
via GitHub·06:09 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

Which installations are affected?

The malicious behavior is in dsh-plugin-blender-3d version 0.2.1. Its postinstall script runs during npm installation, so systems where that version was installed should be treated as fully compromised.

2

Does exploitation require an attacker to have access to the target system after installation?

No. The package executes its postinstall script when npm installs it, downloading and running the payload automatically. Root access or passwordless sudo enables system-wide installation and persistence; without those privileges, it installs a miner in the current user's home directory.

3

What should be done if the package was installed?

Rotate all secrets and keys stored on the affected computer immediately, using a different computer. Remove the package, but do not assume removal eliminates the compromise because the payload may have installed additional malicious software and persistence.

4

How can responders look for evidence of compromise?

Check for a downloaded carrier at /tmp/.smh, random-named systemd units or @reboot cron entries, and random-named directories under ~/.local/lib/. Network activity to networkservicesupp.flashhub.net on port 8443 over TLS may also indicate mining activity.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203