element-guci-utilnpm
element-guci-util is a confirmed malicious npm package (MAL-2026-15880) that executes malicious code on install (malicious versions 7.0.0, 7.1.1, 7.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in element-guci-util (npm)
What this malware does
Package is published as an element-ui utility library (element-guci-util, description '元素-ui 常用工具函数集合') but its main entrypoint contains no utility functions. On require()/import, top-level code invokes iconFont() which checks the current date and, on or after 2026-10-01, invokes iconDont(). iconDont fabricates a synthetic .exe Blob and triggers an anchor click to force a download on the end user, opens https://admin.nikolive.cn/ in a new window, calls location.reload(true) on a 500ms interval, and starts CPU/memory exhaustion loops. Package metadata carries placeholder values (author: '你的名字', repo 你的git仓库地址), and package.json declares the package as its own dependency at ^9.9.9 while publishing as 10.0.0 — a self-referential range disjoint from the published version, which alters what subsequent installs resolve to. Any web application bundling this module will ship the payload to its end users once the trigger date passes; the forced.exe download plus redirect to an attacker-controlled host constitutes an attacker-benefiting payload against the installer's downstream users, not benign vandalism.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for element-guci-util (18 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging element-guci-util across your stack and pipelines.
If you installed it — respond
Remove element-guci-util 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 element-guci-util 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 element-guci-util 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 element-guci-util-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.