@corpweb-ui/wmkt-librarynpm
Malicious code in @corpweb-ui/wmkt-library (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
index.js uses child_process to execute whoami and gather hostname information, then transmits results via https.get to api.telegram.org/bot — a well-known pattern for Telegram-bot-based C2/exfiltration. The package name mimics a corporate UI library but the code performs system reconnaissance and exfiltration of installer host data, with no legitimate UI-library functionality indicated at the entry point. Any installer or build system that pulls this package will leak the machine's user and hostname to an attacker-controlled Telegram bot on require/load. Three independent static detections (child-process + https exfiltration, nodejs system exfiltration, simple sysinfo exfiltration) corroborate a single small file implementing a classic recon beacon.
The OpenSSF Package Analysis project identified '@corpweb-ui/wmkt-library' @ 99.99.11 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @corpweb-ui/wmkt-library (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @corpweb-ui/wmkt-library across your stack and pipelines.
If you installed it — respond
@corpweb-ui/wmkt-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 @corpweb-ui/wmkt-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 @corpweb-ui/wmkt-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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @corpweb-ui/wmkt-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.