NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @uipath published 66 malicious packages. See the full campaign →
Malicious package

@uipath/aops-policy-toolnpm

Advisory published Updated

@uipath/aops-policy-tool is a confirmed malicious npm package (MAL-2026-3528) that steals credentials and exfiltrates sensitive data (malicious version 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @uipath/aops-policy-tool (npm)

MAL-2026-3528
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @uipath/aops-policy-tool

What this malware does

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.

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

1 flagged
0.3.1

Indicators of compromise (SHA-256)

e3ffa653b190d1fd6f355664623366bda5832396e46eb577a6da7e729d642ca5
5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @uipath/aops-policy-tool (version 0.3.1).

  2. If you installed it — respond

    @uipath/aops-policy-tool is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @uipath/aops-policy-tool was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @uipath/aops-policy-tool on npm has been identified as a malicious package (version 0.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qwfj-397c-fjm3

References

Detect & block this

O3 blocks @uipath/aops-policy-tool-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@uipath/aops-policy-tool (npm) malicious package — MAL-2026-3528 | O3 Security