Which versions of uplandui are malicious?

The following npm versions of uplandui are flagged malicious: 0.5.4. Treat any of these as compromised.

How do I remediate uplandui if I installed it?

uplandui 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.

I already installed uplandui — how do I know if it already compromised me?

If uplandui 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 uplandui part of a known attack campaign?

Yes — uplandui is associated with the GHSA-384v-73ff-24g7, RLMA-2026-01634 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 uplandui 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 uplandui (version 0.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uplandui across your stack and pipelines.

Malicious package

uplanduinpm

Malicious code in uplandui (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190938

Immediate action

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

npm uninstall uplandui

What this malware does

The package uplandui was found to contain malicious code.

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 by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.5.4

Indicators of compromise (SHA-256)

e26bf91e39b976ff5aa4107bd8140380fdceeb1de6c12a9fd9993d1ff16642aa

22f9a52e37653e2c0d85c55db9f1173d503391434bb0a2667b8ae8e57f1ed92b

ad95eda4ff338296dfcba32749dfd1f64ccfab52371e8277904a56f6553f5819

9f71fdeebe14c3c5f21f430c23c84a480a7b09a3f1d5e10c76daa6e48779840a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for uplandui (version 0.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uplandui across your stack and pipelines.
If you installed it — respond
uplandui 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.
Did it already run?
If uplandui 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 uplandui 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. uplandui on npm has been identified as a malicious package (version 0.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-384v-73ff-24g7RLMA-2026-01634

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks uplandui-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