@offa-uwk/offa-uwknpm
@offa-uwk/offa-uwk is a confirmed malicious npm package (MAL-2026-12327) that opens a backdoor for remote access (malicious version 999.0.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @offa-uwk/offa-uwk (npm)
What this malware does
On npm install, the package's postinstall script (node index.js) collects host identifiers (os.hostname(), os.userInfo().username, process.cwd()) and POSTs them via HTTPS to a hardcoded webhook.site collector at https://webhook.site/e6b10849-38dc-4280-a8e3-72ab39cfaf65. Immediately after the beacon, the script executes shutdown -h now with a fallback of systemctl poweroff, forcibly powering off the installing host. A preinstall step also writes a marker file to the absolute path /home/OFFA/flag, outside the package directory. Package metadata (name @offa-uwk/offa-uwk, version 999.0.6) is consistent with a proof-of-concept malicious artifact.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @offa-uwk/offa-uwk (version 999.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @offa-uwk/offa-uwk across your stack and pipelines.
If you installed it — respond
@offa-uwk/offa-uwk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @offa-uwk/offa-uwk 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 @offa-uwk/offa-uwk 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 @offa-uwk/offa-uwk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.