accounts-final-formnpm
accounts-final-form is a confirmed malicious npm package (MAL-2026-11504) that executes malicious code on install (malicious versions 0.0.1, 9.9.9, 9.9.10…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in accounts-final-form (npm)
What this malware does
Requiring accounts-final-form auto-runs setup.js via process.nextTick(bootstrap) in index.js. setup.js selects a platform-specific asset path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), fetches it from a list of obfuscated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with DNS fallback to *.dl.well1.site, stages the file under /var/tmp or %TEMP%, chmods it 0755, and executes it via child_process. Destination hostnames and dangerous APIs are constructed by string-splitting and.join("") to evade static analysis (e.g. require("child_"+"process"), os["plat"+"form"], fs["chmod"+"Sync"]). setup.js additionally computes an install fingerprint from os.hostname(), os.userInfo().username, process.cwd(), process.version, and process.pid, hashes it to 16 hex characters, and sends it as installId in the request to the same Workers hosts, enabling per-victim identification. The package's advertised purpose is a vacuous "Accounts final form runtime support module" that does not justify pulling native binaries from anonymous workers.dev subdomains and executing them.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for accounts-final-form (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging accounts-final-form across your stack and pipelines.
If you installed it — respond
Remove accounts-final-form 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 activity or persistence.
Did it already run?
If accounts-final-form 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 accounts-final-form 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 accounts-final-form-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.