forge-jsxynpm
forge-jsxy is a confirmed malicious npm package (MAL-2026-3609) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.103, 1.0.104, 1.0.105…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in forge-jsxy (npm)
What this malware does
forge-jsxy is a malicious npm package part of the same campaign as forge-jsx. It typosquats the name by appending a 'y' and carries an identical fake description ('Node.js integration layer for Autodesk Forge') to impersonate a legitimate Autodesk Forge SDK. The package is a fully-formed RAT deployed from its first published version.
Installing the package on any non-CI machine triggers a multi-stage postinstall chain (postinstall-clipboard-event.mjs, postinstall-bootstrap.mjs, postinstall-agent.mjs) that silently deploys a persistent background agent. The agent captures all keystrokes via native hooks (uiohook-napi), monitors clipboard contents, recursively scans the filesystem for .env files and shell history, steals HuggingFace credentials, and opens a WebSocket-based remote filesystem backdoor for full file browsing and exfiltration. Screenshots are captured and exfiltrated via Discord webhooks. The C2 relay URL is AES-256-GCM encrypted inside the package bundle to hide it from static analysis. Persistence is established across reboots via systemd (Linux), LaunchAgent (macOS), and Task Scheduler (Windows). CI environments (GitHub Actions, GitLab CI, Travis, CircleCI, Jenkins, TeamCity) are detected and skipped to avoid sandbox exposure.
Package ships a postinstall script (scripts/postinstall-agent.mjs) and bundled runtime modules (dist/discordRelayUpload.js, dist/relayServer.js, dist/secretScan/agentStartupAudit.js, dist/hfCredentials.js, dist/deploymentDefaults.js) that include patterns commonly seen in both legitimate integrations and supply-chain attacks: base64-encoded blobs decoded via Buffer.from(..., 'base64'), HTTP POSTs, ping/network probes, and outbound fetches to huggingface.co. The naming and module shape (Discord relay upload, HuggingFace credentials, secret-scan agent startup audit, encode-deployment script, deployment defaults) is consistent with a legitimate developer-tool package that integrates with HuggingFace and Discord, but the combination of a postinstall agent script, base64-decoded deployment defaults, hardcoded credentials module, and a 'discordRelayUpload' path that performs POST requests warrants manual inspection. Without traced-code corroboration of the actual data flows (what is read from the installer's environment, where decoded blobs end up, whether postinstall-agent.mjs auto-fetches or executes remote content), the patterns alone do not establish installer-side harm versus a legitimate integration. Reviewer should specifically verify: (1) whether scripts/postinstall-agent.mjs reaches network destinations or executes fetched bytes at install, (2) what dist/deploymentDefaults.js's base64 blobs decode to and how they are used, (3) whether dist/discordRelayUpload.js POSTs caller-supplied data to a hardcoded Discord webhook (silent-relay shape) or only to user-configured destinations, (4) what dist/hfCredentials.js reads and where it sends it.
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
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for forge-jsxy (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging forge-jsxy across your stack and pipelines.
If you installed it — respond
forge-jsxy 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 forge-jsxy 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-jsxy 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
- SafeDep · finder
Detect & block this
O3 blocks forge-jsxy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.