Which versions of getd-ui-library are malicious?

The following npm versions of getd-ui-library are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate getd-ui-library if I installed it?

getd-ui-library 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 getd-ui-library — how do I know if it already compromised me?

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

Yes — getd-ui-library is associated with the IN-MAL-2026-005204, IN-MAL-2026-005203, GHSA-8h8q-6m6x-v8vv, RLMA-2026-05546 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 getd-ui-library 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 getd-ui-library (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getd-ui-library across your stack and pipelines.

Malicious package

getd-ui-librarynpm

Malicious code in getd-ui-library (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5471

Immediate action

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

npm uninstall getd-ui-library

What this malware does

On npm install, postinstall.js runs unconditionally (scripts.postinstall = 'node postinstall.js') and sends an HTTPS GET to a hardcoded webhook.site URL carrying the installer's hostname (os.hostname()), username (os.userInfo().username), platform (os.platform()), current working directory (process.cwd()), and CI-detection environment variables (CI, BUILD_BUILDID, AGENT_NAME) as query parameters. webhook.site is an anonymous request-capture service — whoever holds the UUID receives identifying telemetry from every machine that installs this package, useful for follow-on targeting (CI build agent fingerprinting, developer host enumeration). Errors from the request are swallowed silently. The package additionally occupies the unscoped name getd-ui-library to mimic the legitimate scoped @getd/ui-library package; any developer who mistypes the install name receives this beacon. The package's own README framing this as 'defensive squat' research does not change the installer-side impact: host/user/cwd identifiers leave the machine on every install with no opt-in.

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

0.0.1

Indicators of compromise (SHA-256)

600dc0698dbd55835d4f128bc75ef8e4722db79a071a4bf4fc5dd6ffbe741448

fcdbf66757b102ed524f01c498adae819b02968aa455f57316f4e08af1fb9ea0

60a3bb3c1ca6e1379dfe85b06cb5166d2331fdb9a28906d1dc5419ecb4b0e50d

a4dac2b5ad4929ad5fc1ea86576f4aff07bad6a4ed39a3314ac2b7b016275e92

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 getd-ui-library (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getd-ui-library across your stack and pipelines.
If you installed it — respond
getd-ui-library 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 getd-ui-library 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 getd-ui-library 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. getd-ui-library on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005204IN-MAL-2026-005203GHSA-8h8q-6m6x-v8vvRLMA-2026-05546

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks getd-ui-library-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