Open Source · · 1 day

UiPath npm packages carried Shai-Hulud

JFrog listed 66 UiPath npm packages 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

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.

Notes

  • The network and payload indicators are the campaign-level set JFrog published for this wave, not observations of this package's own bytes. Indicators read from an acquired sample are marked as such where they appear.
  • Minimal campaign-linked record created to keep Shai-Hulud package evidence scoped by vendor, organization, maintainer account, or package distribution surface.

Appendix · Affected releases

@uipath/access-policy-sdk npm
0.3.1 sha256 13e5a744…39a1a2db sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/access-policy-tool npm
0.3.1 sha256 e836b4f9…863fc4f8 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/admin-tool npm
0.1.1 sha256 fae385ff…e40fa42e sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/agent-sdk npm
1.0.2 sha256 2502c42d…35d1a950 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/agent-tool npm
1.0.1 sha256 691b7abb…63a870de sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/agent.sdk npm
0.0.18 sha256 fd5531ee…fca21e8c sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/aops-policy-tool npm
0.3.1 sha256 646e66cb…da438afb sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/ap-chat npm
1.5.7 sha256 ff8d2c42…3fefb52a sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/api-workflow-tool npm
1.0.1 sha256 a0817cad…112a4257 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/apollo-core npm
5.9.2 sha256 919a91ee…11de1c35 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/apollo-react npm
4.24.5 sha256 51b0fafe…094109ea sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/apollo-wind npm
2.16.2 sha256 7501a74f…b30b6835 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/auth npm
1.0.1 sha256 57bb8c05…b5dc6133 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/case-tool npm
1.0.1 sha256 d4d9cbba…9374e697 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/cli npm
1.0.1 sha256 d9e51482…5c42eb12 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/codedagent-tool npm
1.0.1 sha256 6388b783…a01baa7a sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/codedagents-tool npm
0.1.12 sha256 955b1749…aee0c0b0 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/codedapp-tool npm
1.0.1 sha256 d3b01af7…98aed891 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/common npm
1.0.1 sha256 afd3d136…1e16ecf2 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/context-grounding-tool npm
0.1.1 sha256 82f26585…13029447 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/data-fabric-tool npm
1.0.2 sha256 87050c14…e0319b4b sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/docsai-tool npm
1.0.1 sha256 93c1d6fa…32ff8101 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/filesystem npm
1.0.1 sha256 608af385…40f0e861 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/flow-tool npm
1.0.2 sha256 0afac963…b5d0238e sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/functions-tool npm
1.0.1 sha256 496268b6…e3abf76f sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/gov-tool npm
0.3.1 sha256 c080e7ec…11d180b4 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/identity-tool npm
0.1.1 sha256 64c6b5fb…d3564cff sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/insights-sdk npm
1.0.1 sha256 551d6692…ad5e7745 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/insights-tool npm
1.0.1 sha256 06f43baa…b49022ca sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/integrationservice-sdk npm
1.0.2 sha256 a2a6af3d…d633d6e3 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/integrationservice-tool npm
1.0.2 sha256 71d326b3…ea2d6f37 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/llmgw-tool npm
1.0.1 sha256 a4386c4d…f0373ccd sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/maestro-sdk npm
1.0.1 sha256 b11a9102…ca6039ec sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/maestro-tool npm
1.0.1 sha256 cd3486ee…f9596256 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/orchestrator-tool npm
1.0.1 sha256 37bd5016…2e96cd4f sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-apiworkflow npm
0.0.19 sha256 a74a2070…34f727ec sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-bpmn npm
0.0.9 sha256 eb43e2ff…77bd7a85 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-case npm
0.0.9 sha256 fd337054…cba357bd sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-connector npm
0.0.19 sha256 64e9990b…87bebb76 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-flow npm
0.0.19 sha256 2019665d…b062e4db sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-functions npm
0.1.1 sha256 13315b97…1daa8e2b sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-webapp npm
1.0.6 sha256 9096c14d…ad6d9826 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-workflowcompiler npm
0.0.16 sha256 223a5c97…2f9223b3 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/packager-tool-workflowcompiler-browser npm
0.0.34 sha256 55bf7826…00f7d2c3 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/platform-tool npm
1.0.1 sha256 4fcb7932…6ea4f7f5 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/project-packager npm
1.1.16 sha256 36c7537c…0f3ce5a9 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/resource-tool npm
1.0.1 sha256 901c63bc…1e389429 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/resourcecatalog-tool npm
0.1.1 sha256 5dd5ab06…7a688ebd sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/resources-tool npm
0.1.11 sha256 178cff42…2ac6ba87 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/robot npm
1.3.4 sha256 d1058b5a…7eb14eee sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/rpa-legacy-tool npm
1.0.1 sha256 8ff2ee4f…be33cbdc sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/rpa-tool npm
0.9.5 sha256 7d66a342…8c80c04f sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/solution-packager npm
0.0.35 sha256 fc500763…d9031102 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/solution-tool npm
1.0.1 sha256 9a6205cc…d444b864 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/solutionpackager-sdk npm
1.0.11 sha256 fddd19fa…a40044a9 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/solutionpackager-tool-core npm
0.0.34 sha256 11c20957…ecc2f224 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/tasks-tool npm
1.0.1 sha256 db2df00d…19fedace sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/telemetry npm
0.0.7 sha256 cda27823…d82cc19b sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/test-manager-tool npm
1.0.2 sha256 79a40553…e2c63370 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/tool-workflowcompiler npm
0.0.12 sha256 facadcac…8d93b14c sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/traces-tool npm
1.0.1 sha256 20d873f6…5b921224 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/ui-widgets-multi-file-upload npm
1.0.1 sha256 3f954d71…7d6df284 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/uipath-python-bridge npm
1.0.1 sha256 b2d39857…fa39abdd sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/vertical-solutions-tool npm
1.0.1 sha256 15f007c3…6ec7dedb sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/vss npm
0.1.6 sha256 7a673295…95c6f9d0 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.
@uipath/widget.sdk npm
1.2.3 sha256 3e0c4857…41c22d47 sample in lab ↗
  • A complete attack tree is retained as a clearly named RECONSTRUCTED sample. No hashes are recorded because no authoritative checksum for the removed npm archive is known; the synthetic digest and method are in samples/manifest.yaml.

66 samples linked above. Analysis and downloads are available in the lab.

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_author[email protected]

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. Socket package file listing for @uipath/access-policy-sdk 0.3.1socket.dev
  4. Socket package file listing for @uipath/access-policy-tool 0.3.1socket.dev
  5. Socket package file listing for @uipath/admin-tool 0.1.1socket.dev
  6. Socket package file listing for @uipath/agent-sdk 1.0.2socket.dev
  7. Socket package file listing for @uipath/agent-tool 1.0.1socket.dev
  8. Socket package file listing for @uipath/agent.sdk 0.0.18socket.dev
  9. Socket package file listing for @uipath/aops-policy-tool 0.3.1socket.dev
  10. Socket package file listing for @uipath/ap-chat 1.5.7socket.dev
  11. Socket package file listing for @uipath/api-workflow-tool 1.0.1socket.dev
  12. Socket package file listing for @uipath/apollo-core 5.9.2socket.dev
  13. Socket package file listing for @uipath/apollo-react 4.24.5socket.dev
  14. Socket package file listing for @uipath/apollo-wind 2.16.2socket.dev
  15. Socket package file listing for @uipath/auth 1.0.1socket.dev
  16. Socket package file listing for @uipath/case-tool 1.0.1socket.dev
  17. Socket package file listing for @uipath/cli 1.0.1socket.dev
  18. Socket package file listing for @uipath/codedagent-tool 1.0.1socket.dev
  19. Socket package file listing for @uipath/codedagents-tool 0.1.12socket.dev
  20. Socket package file listing for @uipath/codedapp-tool 1.0.1socket.dev
  21. Socket package file listing for @uipath/common 1.0.1socket.dev
  22. Socket package file listing for @uipath/context-grounding-tool 0.1.1socket.dev
  23. Socket package file listing for @uipath/data-fabric-tool 1.0.2socket.dev
  24. Socket package file listing for @uipath/docsai-tool 1.0.1socket.dev
  25. Socket package file listing for @uipath/filesystem 1.0.1socket.dev
  26. Socket package file listing for @uipath/flow-tool 1.0.2socket.dev
  27. Socket package file listing for @uipath/functions-tool 1.0.1socket.dev
  28. Socket package file listing for @uipath/gov-tool 0.3.1socket.dev
  29. Socket package file listing for @uipath/identity-tool 0.1.1socket.dev
  30. Socket package file listing for @uipath/insights-sdk 1.0.1socket.dev
  31. Socket package file listing for @uipath/insights-tool 1.0.1socket.dev
  32. Socket package file listing for @uipath/integrationservice-sdk 1.0.2socket.dev
  33. Socket package file listing for @uipath/integrationservice-tool 1.0.2socket.dev
  34. Socket package file listing for @uipath/llmgw-tool 1.0.1socket.dev
  35. Socket package file listing for @uipath/maestro-sdk 1.0.1socket.dev
  36. Socket package file listing for @uipath/maestro-tool 1.0.1socket.dev
  37. Socket package file listing for @uipath/orchestrator-tool 1.0.1socket.dev
  38. Socket package file listing for @uipath/packager-tool-apiworkflow 0.0.19socket.dev
  39. Socket package file listing for @uipath/packager-tool-bpmn 0.0.9socket.dev
  40. Socket package file listing for @uipath/packager-tool-case 0.0.9socket.dev
  41. Socket package file listing for @uipath/packager-tool-connector 0.0.19socket.dev
  42. Socket package file listing for @uipath/packager-tool-flow 0.0.19socket.dev
  43. Socket package file listing for @uipath/packager-tool-functions 0.1.1socket.dev
  44. Socket package file listing for @uipath/packager-tool-webapp 1.0.6socket.dev
  45. Socket package file listing for @uipath/packager-tool-workflowcompiler 0.0.16socket.dev
  46. Socket package file listing for @uipath/packager-tool-workflowcompiler-browser 0.0.34socket.dev
  47. Socket package file listing for @uipath/platform-tool 1.0.1socket.dev
  48. Socket package file listing for @uipath/project-packager 1.1.16socket.dev
  49. Socket package file listing for @uipath/resource-tool 1.0.1socket.dev
  50. Socket package file listing for @uipath/resourcecatalog-tool 0.1.1socket.dev
  51. Socket package file listing for @uipath/resources-tool 0.1.11socket.dev
  52. Socket package file listing for @uipath/robot 1.3.4socket.dev
  53. Socket package file listing for @uipath/rpa-legacy-tool 1.0.1socket.dev
  54. Socket package file listing for @uipath/rpa-tool 0.9.5socket.dev
  55. Socket package file listing for @uipath/solution-packager 0.0.35socket.dev
  56. Socket package file listing for @uipath/solution-tool 1.0.1socket.dev
  57. Socket package file listing for @uipath/solutionpackager-sdk 1.0.11socket.dev
  58. Socket package file listing for @uipath/solutionpackager-tool-core 0.0.34socket.dev
  59. Socket package file listing for @uipath/tasks-tool 1.0.1socket.dev
  60. Socket package file listing for @uipath/telemetry 0.0.7socket.dev
  61. Socket package file listing for @uipath/test-manager-tool 1.0.2socket.dev
  62. Socket package file listing for @uipath/tool-workflowcompiler 0.0.12socket.dev
  63. Socket package file listing for @uipath/traces-tool 1.0.1socket.dev
  64. Socket package file listing for @uipath/ui-widgets-multi-file-upload 1.0.1socket.dev
  65. Socket package file listing for @uipath/uipath-python-bridge 1.0.1socket.dev
  66. Socket package file listing for @uipath/vertical-solutions-tool 1.0.1socket.dev
  67. Socket package file listing for @uipath/vss 0.1.6socket.dev
  68. Socket package file listing for @uipath/widget.sdk 1.2.3socket.dev
  69. Mini Shai-Hulud Is Back: npm Worm Hits over 160 Packages, including Mistral and Tanstack - Aikidoaikido.dev
  70. Socket package file listing for clean predecessor @uipath/apollo-core 5.9.1socket.dev
  71. Socket package file listing for clean predecessor @uipath/apollo-react 4.24.4socket.dev
  72. Socket package file listing for clean predecessor @uipath/ap-chat 1.5.6socket.dev
  73. npm registry metadata for clean predecessor @uipath/apollo-core 5.9.1registry.npmjs.org
  74. npm registry metadata for clean predecessor @uipath/apollo-react 4.24.4registry.npmjs.org
  75. npm registry metadata for clean predecessor @uipath/ap-chat 1.5.6registry.npmjs.org
  76. Socket API file listing for clean predecessor @uipath/access-policy-sdk 0.3.0socket.dev
  77. npm registry metadata for clean predecessor @uipath/access-policy-sdk 0.3.0registry.npmjs.org
  78. Socket API file listing for clean predecessor @uipath/admin-tool 0.1.0socket.dev
  79. npm registry metadata for clean predecessor @uipath/admin-tool 0.1.0registry.npmjs.org
  80. Socket API file listing for clean predecessor @uipath/agent-sdk 1.0.1socket.dev
  81. npm registry metadata for clean predecessor @uipath/agent-sdk 1.0.1registry.npmjs.org
  82. Socket API file listing for clean predecessor @uipath/aops-policy-tool 0.3.0socket.dev
  83. npm registry metadata for clean predecessor @uipath/aops-policy-tool 0.3.0registry.npmjs.org
  84. Socket API file listing for clean predecessor @uipath/auth 1.0.0socket.dev
  85. npm registry metadata for clean predecessor @uipath/auth 1.0.0registry.npmjs.org
  86. Socket API file listing for clean predecessor @uipath/cli 1.0.0socket.dev
  87. npm registry metadata for clean predecessor @uipath/cli 1.0.0registry.npmjs.org
  88. Socket API file listing for clean predecessor @uipath/common 1.0.0socket.dev
  89. npm registry metadata for clean predecessor @uipath/common 1.0.0registry.npmjs.org
  90. Socket API file listing for clean predecessor @uipath/functions-tool 1.0.0socket.dev
  91. npm registry metadata for clean predecessor @uipath/functions-tool 1.0.0registry.npmjs.org
  92. Socket API file listing for clean predecessor @uipath/gov-tool 0.3.0socket.dev
  93. npm registry metadata for clean predecessor @uipath/gov-tool 0.3.0registry.npmjs.org
  94. Socket API file listing for clean predecessor @uipath/insights-sdk 1.0.0socket.dev
  95. npm registry metadata for clean predecessor @uipath/insights-sdk 1.0.0registry.npmjs.org
  96. Socket API file listing for clean predecessor @uipath/integrationservice-sdk 1.0.1socket.dev
  97. npm registry metadata for clean predecessor @uipath/integrationservice-sdk 1.0.1registry.npmjs.org
  98. Socket API file listing for clean predecessor @uipath/llmgw-tool 1.0.0socket.dev
  99. npm registry metadata for clean predecessor @uipath/llmgw-tool 1.0.0registry.npmjs.org
  100. Socket API file listing for clean predecessor @uipath/resources-tool 0.1.10socket.dev
  101. npm registry metadata for clean predecessor @uipath/resources-tool 0.1.10registry.npmjs.org
  102. Socket API file listing for clean predecessor @uipath/traces-tool 1.0.0socket.dev
  103. npm registry metadata for clean predecessor @uipath/traces-tool 1.0.0registry.npmjs.org
  104. Socket API file listing for clean predecessor @uipath/ui-widgets-multi-file-upload 1.0.0socket.dev
  105. npm registry metadata for clean predecessor @uipath/ui-widgets-multi-file-upload 1.0.0registry.npmjs.org
  106. Socket API file listing for clean predecessor @uipath/access-policy-tool 0.3.0socket.dev
  107. npm registry metadata for clean predecessor @uipath/access-policy-tool 0.3.0registry.npmjs.org
  108. Socket API file listing for clean predecessor @uipath/agent-tool 1.0.0socket.dev
  109. npm registry metadata for clean predecessor @uipath/agent-tool 1.0.0registry.npmjs.org
  110. Socket API file listing for clean predecessor @uipath/agent.sdk 0.0.17socket.dev
  111. npm registry metadata for clean predecessor @uipath/agent.sdk 0.0.17registry.npmjs.org
  112. Socket API file listing for clean predecessor @uipath/api-workflow-tool 1.0.0socket.dev
  113. npm registry metadata for clean predecessor @uipath/api-workflow-tool 1.0.0registry.npmjs.org
  114. Socket API file listing for clean predecessor @uipath/apollo-wind 2.16.1socket.dev
  115. npm registry metadata for clean predecessor @uipath/apollo-wind 2.16.1registry.npmjs.org
  116. Socket API file listing for clean predecessor @uipath/case-tool 1.0.0socket.dev
  117. npm registry metadata for clean predecessor @uipath/case-tool 1.0.0registry.npmjs.org
  118. Socket API file listing for clean predecessor @uipath/codedapp-tool 1.0.0socket.dev
  119. npm registry metadata for clean predecessor @uipath/codedapp-tool 1.0.0registry.npmjs.org
  120. Socket API file listing for clean predecessor @uipath/data-fabric-tool 1.0.1socket.dev
  121. npm registry metadata for clean predecessor @uipath/data-fabric-tool 1.0.1registry.npmjs.org
  122. Socket API file listing for clean predecessor @uipath/docsai-tool 1.0.0socket.dev
  123. npm registry metadata for clean predecessor @uipath/docsai-tool 1.0.0registry.npmjs.org
  124. Socket API file listing for clean predecessor @uipath/flow-tool 1.0.1socket.dev
  125. npm registry metadata for clean predecessor @uipath/flow-tool 1.0.1registry.npmjs.org
  126. Socket API file listing for clean predecessor @uipath/identity-tool 0.1.0socket.dev
  127. npm registry metadata for clean predecessor @uipath/identity-tool 0.1.0registry.npmjs.org
  128. Socket API file listing for clean predecessor @uipath/insights-tool 1.0.0socket.dev
  129. npm registry metadata for clean predecessor @uipath/insights-tool 1.0.0registry.npmjs.org
  130. Socket API file listing for clean predecessor @uipath/integrationservice-tool 1.0.1socket.dev
  131. npm registry metadata for clean predecessor @uipath/integrationservice-tool 1.0.1registry.npmjs.org
  132. Socket API file listing for clean predecessor @uipath/maestro-sdk 1.0.0socket.dev
  133. npm registry metadata for clean predecessor @uipath/maestro-sdk 1.0.0registry.npmjs.org
  134. Socket API file listing for clean predecessor @uipath/maestro-tool 1.0.0socket.dev
  135. npm registry metadata for clean predecessor @uipath/maestro-tool 1.0.0registry.npmjs.org
  136. Socket API file listing for clean predecessor @uipath/orchestrator-tool 1.0.0socket.dev
  137. npm registry metadata for clean predecessor @uipath/orchestrator-tool 1.0.0registry.npmjs.org
  138. Socket API file listing for clean predecessor @uipath/platform-tool 1.0.0socket.dev
  139. npm registry metadata for clean predecessor @uipath/platform-tool 1.0.0registry.npmjs.org
  140. Socket API file listing for clean predecessor @uipath/project-packager 1.1.15socket.dev
  141. npm registry metadata for clean predecessor @uipath/project-packager 1.1.15registry.npmjs.org
  142. Socket API file listing for clean predecessor @uipath/resource-tool 1.0.0socket.dev
  143. npm registry metadata for clean predecessor @uipath/resource-tool 1.0.0registry.npmjs.org
  144. Socket API file listing for clean predecessor @uipath/resourcecatalog-tool 0.1.0socket.dev
  145. npm registry metadata for clean predecessor @uipath/resourcecatalog-tool 0.1.0registry.npmjs.org
  146. Socket API file listing for clean predecessor @uipath/robot 1.3.3socket.dev
  147. npm registry metadata for clean predecessor @uipath/robot 1.3.3registry.npmjs.org
  148. Socket API file listing for clean predecessor @uipath/rpa-legacy-tool 1.0.0socket.dev
  149. npm registry metadata for clean predecessor @uipath/rpa-legacy-tool 1.0.0registry.npmjs.org
  150. Socket API file listing for clean predecessor @uipath/rpa-tool 0.9.4socket.dev
  151. npm registry metadata for clean predecessor @uipath/rpa-tool 0.9.4registry.npmjs.org
  152. Socket API file listing for clean predecessor @uipath/solution-tool 1.0.0socket.dev
  153. npm registry metadata for clean predecessor @uipath/solution-tool 1.0.0registry.npmjs.org
  154. Socket API file listing for clean predecessor @uipath/solutionpackager-sdk 1.0.10socket.dev
  155. npm registry metadata for clean predecessor @uipath/solutionpackager-sdk 1.0.10registry.npmjs.org
  156. Socket API file listing for clean predecessor @uipath/tasks-tool 1.0.0socket.dev
  157. npm registry metadata for clean predecessor @uipath/tasks-tool 1.0.0registry.npmjs.org
  158. Socket API file listing for clean predecessor @uipath/test-manager-tool 1.0.1socket.dev
  159. npm registry metadata for clean predecessor @uipath/test-manager-tool 1.0.1registry.npmjs.org
  160. Socket API file listing for clean predecessor @uipath/vertical-solutions-tool 1.0.0socket.dev
  161. npm registry metadata for clean predecessor @uipath/vertical-solutions-tool 1.0.0registry.npmjs.org
  162. Socket API file listing for clean predecessor @uipath/vss 0.1.5socket.dev
  163. npm registry metadata for clean predecessor @uipath/vss 0.1.5registry.npmjs.org

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