@giftyhq/widget-componentsnpm
Malicious code in @giftyhq/widget-components (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares "preinstall": "node index.js", which fires automatically on npm install. index.js collects host fingerprinting data — os.hostname(), os.userInfo(), process.platform, uid/gid, shell, cwd, and the output of child_process.exec('whoami') and exec('id') — and POSTs the result as JSON to the hardcoded URL https://zad79wtflht20n15czfieir3quwlkb80.oastify.com/detox56. The destination is a Burp Collaborator (oastify.com) out-of-band subdomain used as attacker-controlled exfiltration infrastructure. The package ships no legitimate component code; metadata is empty (no author, no description) and the package's only effect is the install-time recon beacon. Name and scope are consistent with a dependency-confusion / namespace-squat lure.
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 @giftyhq/widget-components (version 19.12.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @giftyhq/widget-components across your stack and pipelines.
If you installed it — respond
@giftyhq/widget-components 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 @giftyhq/widget-components 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 @giftyhq/widget-components 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 @giftyhq/widget-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.