Which versions of forge-extended are malicious?

The following npm versions of forge-extended are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate forge-extended if I installed it?

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.

I already installed forge-extended — how do I know if it already compromised me?

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.

Is forge-extended part of a known attack campaign?

Yes — forge-extended is associated with the IN-MAL-2026-011495 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find forge-extended across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for forge-extended (version 1.0.1). 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.

Malicious package

forge-extendednpm

forge-extended is a confirmed malicious npm package (MAL-2026-12040) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in forge-extended (npm)

MAL-2026-12040

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall forge-extended

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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

3784f08ba715b7afbeecfaa10b9c953b4406770c976bd07200977fa2f80b0317

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for forge-extended (version 1.0.1). 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

No. forge-extended on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011495

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database