Which versions of uhd-setup are malicious?

The following npm versions of uhd-setup are flagged malicious: 0.0.1-security-research, 99.0.0. Treat any of these as compromised.

How do I remediate uhd-setup if I installed it?

Remove uhd-setup 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is uhd-setup part of a known attack campaign?

Yes — uhd-setup is associated with the IN-MAL-2026-005244, IN-MAL-2026-005243 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect uhd-setup in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking uhd-setup and packages like it before any post-install script runs.

Malicious package

uhd-setupnpm

Malicious code in uhd-setup (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5287

Immediate action

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

npm uninstall uhd-setup

What this malware does

package.json declares scripts.preinstall: node index.js. On npm install, index.js (lines 4-5) performs dns.resolve and https.get against <id>.d8hiivedv3ok8hrng5eghchyw4hwsioaz.oast.online, an Interactsh OAST collector. The request fires unconditionally with no opt-out, leaking the installer's egress IP, internal DNS resolver identity, and fact-of-install (with the package id encoded in the subdomain and URL path) to a third-party-controlled endpoint. The README frames this as authorized dependency-confusion research targeting Ubiquiti, but the beacon does not gate on any organizational identifier — any installer that pulls this name (typo, internal-name collision, automated mirror) sends build-system metadata to the researcher. Trigger is the preinstall lifecycle hook, so the network call fires before any code review opportunity.

The OpenSSF Package Analysis project identified 'uhd-setup' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.0.1-security-research99.0.0

Indicators of compromise (SHA-256)

358eee34aaba61eaa93e977d35a18f35f59a56527d7c20b6e9a0bdf9c4a0a8da

7cf641e43172371f2f9c843ad0b68bad139485231e30e9ef8072197977d9f2d5

8cd16b0b6896b16874da441b7197b846bf0c725dcff0ef2d6e8f93c6cc08fc99

Frequently asked questions

No. uhd-setup on npm has been identified as a malicious package (versions 0.0.1-security-research, 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005244IN-MAL-2026-005243

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection