Which versions of uipath-sugar-sell are malicious?

The following npm versions of uipath-sugar-sell are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate uipath-sugar-sell if I installed it?

Remove uipath-sugar-sell from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed uipath-sugar-sell — how do I know if it already compromised me?

If uipath-sugar-sell was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is uipath-sugar-sell part of a known attack campaign?

Yes — uipath-sugar-sell is associated with the IN-MAL-2026-005055, IN-MAL-2026-005056, GHSA-xc4q-c25v-qv6v 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 uipath-sugar-sell across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for uipath-sugar-sell (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uipath-sugar-sell across your stack and pipelines.

Malicious package

uipath-sugar-sellnpm

Malicious code in uipath-sugar-sell (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5455

Immediate action

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

npm uninstall uipath-sugar-sell

What this malware does

Package [email protected] exhibits the canonical dependency-confusion shape: an internal-sounding name targeting a UiPath/SugarSell namespace, a 99.9.1 version overshoot designed to win semver resolution against any private registry, an empty index.js (module.exports = {}) so the package provides no actual functionality, and a single dependency ltidisafe declared as a direct URL https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.7.8.tgz. The path segment depenconf is explicit naming of the dependency-confusion technique. Installing this package causes npm to fetch and install the off-registry tarball from the Google Cloud Storage bucket, bypassing the public registry's audit surface; any lifecycle scripts in that tarball execute on the installer's machine at npm install time, and the tarball contents are mutable by whoever controls the bucket.

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

70cd5d70323e92395a2ea8f61a4089f1cca94e4bb81a7cad1375ae47d3461e6f

ed7b735f00928b9124be0c9baa0e069e8ac61d303725b62584a17e31be8de57e

79e777e1ac88cd9709d47f24704b0889436cfc0f1b3a1738a5009b0500301e2f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for uipath-sugar-sell (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uipath-sugar-sell across your stack and pipelines.
If you installed it — respond
Remove uipath-sugar-sell from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If uipath-sugar-sell was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks uipath-sugar-sell before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. uipath-sugar-sell on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005055IN-MAL-2026-005056GHSA-xc4q-c25v-qv6v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks uipath-sugar-sell-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring