Open Source · · 1 day

Dirigible AI npm package carried Shai-Hulud

JFrog listed 1 Dirigible AI npm package in the May 2026 Shai-Hulud wave. This record scopes those artifacts to their own official distribution surface.

Part of Shai-Hulud hits npm and PyPI campaign

Dirigible AI appeared in the May 2026 Shai-Hulud list through @dirigible-ai/sdk. JFrog listed two affected npm releases, 0.6.2 and 0.6.3, placing the compromise inside an SDK distribution channel rather than a throwaway package name.

SDKs are useful supply-chain targets because they are installed by developers who are connecting services, credentials, and automation together. In the Shai-Hulud wave, TeamPCP used that install-time position to run credential-stealing code and look for tokens that could publish the next infected package.

This record scopes the Dirigible AI package as one compromised trust boundary. The campaign page carries the common malware behavior, infrastructure, and propagation model. This page keeps the artifact list precise enough for lockfile searches, package-cache review, and dependency-management alerts.

The key exposure question is whether any trusted environment resolved @dirigible-ai/sdk to the affected releases during May 11-12. If it did, the package install itself is the incident, regardless of whether the SDK was later imported by application code.

Notes

  • The network and payload indicators are the campaign-level set JFrog published for this wave, not observations of this package's own bytes. They identify the wave's infrastructure and persistence, and are recorded here so each affected distribution surface carries them. Where a record also lists indicators read from an acquired sample, those are marked as such.
  • Minimal campaign-linked record created to keep Shai-Hulud package evidence scoped by vendor, organization, maintainer account, or package distribution surface.

Appendix · Affected releases

Indicators

  • file_sha256npm payload 29c729852fce5a53e30a1541d9fec79c915b2e13f1eda94a5978cf0aae0d88d9
  • file_sha256npm payload 2ec78d556d696e208927cc503d48e4b5eb56b31abc2870c2ed2e98d6be27fc96
  • file_sha256npm payload ab4fcadaec49c03278063dd269ea5eef82d24f2124a8e15d7b90f2fa8601266c
  • file_sha256npm payload d4a2086ea18f5e39cd867b8b06918a524eabb21d45ea98aad07357b98173458a
  • urlhttps://filev2.getsession.org/file/
  • domainseed1.getsession.org
  • domainseed2.getsession.org
  • domainseed3.getsession.org
  • domainapi.masscan.cloud
  • file~/.local/bin/gh-token-monitor.sh
  • file~/.config/systemd/user/gh-token-monitor.service
  • file~/Library/LaunchAgents/com.user.gh-token-monitor.plist
  • file~/.config/gh-token-monitor/
  • stringShai-Hulud: Here We Go Again
  • stringPUSH UR T3MPRR
  • stringFIRESCALE
  • commit_authorclaude@users.noreply.github.com

References

  1. Shai-Hulud: Here We Go Again - Worm by TeamPCP Hits NPM and PyPIresearch.jfrog.com
  2. TanStack npm Packages Compromised in Ongoing Mini Shai-Hulud Supply Chain Attack - Socketsocket.dev
  3. Mini Shai-Hulud Is Back: npm Worm Hits over 160 Packages, including Mistral and Tanstack - Aikidoaikido.dev
  4. Socket retained file tree for @dirigible-ai/sdk 0.6.2socket.dev
  5. Socket retained file tree for @dirigible-ai/sdk 0.6.3socket.dev
  6. Retained jsDelivr flat member manifest for @dirigible-ai/sdk 0.6.3data.jsdelivr.com
  7. Triage report for the exact shared router_init.js payloadtria.ge

Source record: oss/attacks/shai-hulud-dirigible-ai-npm/meta.yaml