Open Source 2026-05-11 · 1 day ·Credential Theft, Self Propagation

UiPath npm packages carried Shai-Hulud

Part of the Shai-Hulud hits npm and PyPI campaign

JFrog listed 66 UiPath npm packages in the May 2026 Shai-Hulud wave. This record scopes those artifacts to their own official distribution surface.

Story

UiPath was one of the largest namespace entries in the May 2026 Shai-Hulud wave. JFrog listed 66 affected @uipath/* npm packages, spanning access-policy tools, admin tooling, agent packages, chat components, and other automation-adjacent modules.

That breadth matters because UiPath packages are likely to be used by teams building automation and integration workflows. Those environments often contain service credentials, repository tokens, cloud configuration, and deployment authority. Shai-Hulud's install-time payload was designed to harvest exactly that context and use any publishing access it found.

This record keeps the UiPath namespace as a separate trust boundary rather than burying it inside the campaign total. The campaign page carries TeamPCP's shared loader, infrastructure, credential theft, and self-propagation behavior; this page preserves the exact package list, versions, registry paths, and May 11-12 exposure window.

Response should start with a namespace-wide inventory sweep. Lockfiles, package caches, private mirrors, build images, and CI logs should be checked for the listed @uipath/* packages, and any installing environment with package-publishing or deployment authority should be treated as a possible source of further compromise.

Affected Artifacts

Incident Context

Motive
Credential Theft
Attribution
Group
Cause
Compromised Account Credentials
Transitive
Yes
Actor
TeamPCP

Notes

  • Minimal campaign-linked record created to keep Shai-Hulud package evidence scoped by vendor, organization, maintainer account, or package distribution surface.

External References

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