forge-extendednpm
forge-extended is a confirmed malicious npm package (MAL-2026-12040) that opens a backdoor for remote access (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in forge-extended (npm)
What this malware does
On npm install, the package's preinstall script (index.js) collects installer-side system data — os.hostname(), os.userInfo().username, home directory, DNS server list, and package metadata — reads /etc/passwd and /etc/hosts from the installer's filesystem, and POSTs the aggregated JSON payload over HTTPS to the Burp Collaborator subdomain 67bqctsh977zz60hiszvr1pbc2iu6ku9.oastify.com. The behavior fires automatically as a lifecycle hook, without any user action beyond installation. The oastify.com destination is an out-of-band recon endpoint unrelated to any documented purpose of the package, and the payload structure (host identity + /etc/passwd + /etc/hosts) is a canonical dependency-confusion / reconnaissance beacon.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for forge-extended (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging forge-extended across your stack and pipelines.
If you installed it — respond
forge-extended 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 forge-extended 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 forge-extended 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 forge-extended-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.