@uh-platform/domain-widgetnpm
@uh-platform/domain-widget is a confirmed malicious npm package (MAL-2026-16359) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @uh-platform/domain-widget (npm)
What this malware does
Package @uh-platform/[email protected] is a scoped placeholder with an empty author, generic description, and no real functionality. Its package.json declares scripts.preinstall = "node index.js", and index.js shells out via exec() to curl a hardcoded Burp Collaborator subdomain at http://pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com/. On npm install, the installer's host performs a DNS+HTTP request to that attacker-controlled OAST endpoint, disclosing the installer's IP and host presence and confirming out-of-band code execution on the build machine. The @uh-platform scope combined with an inflated 100.0.0 version, empty metadata, and a preinstall-only payload is the canonical dependency-confusion shape targeting an internal namespace to shadow a private package during resolution.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @uh-platform/domain-widget (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @uh-platform/domain-widget across your stack and pipelines.
If you installed it — respond
Remove @uh-platform/domain-widget 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 @uh-platform/domain-widget 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 @uh-platform/domain-widget 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @uh-platform/domain-widget-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.