ui-weavenpm
Advisory published Updated
ui-weave is a confirmed malicious npm package (MAL-2026-5406) that typosquats a legitimate package to trick installs (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ui-weave (npm)
What this malware does
package.json declares postinstall: node lib/utils/index.js, which spawns a detached child process running lib/utils/smtp-connection/index.js. That script fetches https://www.jsonkeeper.com/b/QHDXR and feeds the response's data.cookie field directly into new Function('require', data.cookie)(require), executing whatever JavaScript is hosted at that URL on every machine that runs npm install ui-weave. jsonkeeper.com is a public, mutable, anonymous paste host — the author can change the served payload at any time without republishing the package. The detached/unref'd spawn is intended to outlive the install command. The package additionally impersonates nodemailer: it ships nodemailer's source under lib/nodemailer.js, claims author Andris Reinman (the real nodemailer maintainer), and copies an unrelated React Training copyright string as its description, while being published under the unrelated name ui-weave with homepage ui-weave.com. The impersonation provides a veneer of legitimacy for the install-time remote-code-execution payload.
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for ui-weave (version 1.0.3).
If you installed it — respond
ui-weave is a typosquat — you almost certainly intended a legitimately-named package. Remove ui-weave, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ui-weave 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ui-weave-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.