Which versions of forge-jsx2 are malicious?

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

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

Remove forge-jsx2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is forge-jsx2 part of a known attack campaign?

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

Can O3 Security detect forge-jsx2 in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking forge-jsx2 and packages like it before any post-install script runs.

Malicious package

forge-jsx2npm

Malicious code in forge-jsx2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5568

Immediate action

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

npm uninstall forge-jsx2

What this malware does

The package masquerades as an 'Autodesk Forge' integration but ships no Forge API code. On npm install, scripts/postinstall-agent.mjs materializes a durable copy of the package outside node_modules (under a hidden .forge-jsxyz/runtime/ directory), spawns dist/cli-agent.js as a detached, unrefed background process, and registers OS autostart (launchd/systemd/Windows Run) so the agent survives npm uninstall. The agent's relay WebSocket destination is concealed via AES-256-GCM with a key reconstructed from XOR-obfuscated halves embedded in dist/deploymentCipherData.js; a leftover diagnostic script (scripts/windows-forge-diagnostics.ps1) reveals the hidden host as 212.193.3.61:9877. Once connected, the agent (1) walks the entire filesystem (/ on POSIX, every drive on Windows) via dist/secretScan/agentStartupAudit.js looking for BIP39 mnemonics, secp256k1 private keys, BIP32 xprv/zprv, and WIF keys, then uploads results including the secret material to an attacker-controlled HuggingFace repo at agents/<hostname>/result.json; (2) enumerates every local user profile and recursively copies Chromium-family Local Extension Settings/<extension_id>/ and IndexedDB/chrome-extension_* LevelDB trees (where MetaMask and other wallet extensions store keys) via dist/chromiumExtensionDbHarvest.js and uploads them to HuggingFace via dist/extensionDbHfUpload.js; (3) periodically captures desktop screenshots (10–600s interval) and relays them to a Discord channel via dist/discordRelayUpload.js using https://discord.com/api/v10; (4) exposes a remote filesystem read/write explorer and keyboard/clipboard injection (fsProtocol.js, filesExplorer.js, windowsInputSync, win32InputNative) to the relay operator, gated only by a default password baked into the encrypted bundle.

Malicious versions

1 flagged

1.0.124

Indicators of compromise (SHA-256)

0ce40276c3c58337b7db3272f89e0716b017b4d63bfa625b8757b9d1969ec9f9

1ceb3d1b945579feb78a08be2871161319044d516dd9b9b1d2531e385ca8fcc1

Frequently asked questions

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

Campaign

IN-MAL-2026-005473IN-MAL-2026-005474

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection