@eforms/forms-apinpm
Advisory published Updated
@eforms/forms-api is a confirmed malicious npm package (MAL-2026-18252) that opens a backdoor for remote access (malicious versions 1.99.0, 1.99.1, 2.0.0-SNAPSHOT…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @eforms/forms-api (npm)
What this malware does
The npm package @eforms/[email protected] is a scoped-name dependency-confusion lure with an inflated version number and an empty index.js stub. Its only functionality is a preinstall lifecycle script (preinstall.js) that runs automatically on npm install. The script reads os.hostname(), os.userInfo() (username and uid), process.cwd(), process.platform, process.arch, process.version, the CI environment flag, and other host identifiers, and transmits them out-of-band to two hardcoded attacker-controlled subdomains of oastify.com (Interactsh / Burp Collaborator OOB infrastructure) — specifically rpkfvtsptfrhcgbe62qg11ywjnpij6ma1cfpke.oastify.com and f6mk7lyjsuk3u1t49ypp9q2jbah15rtg.oastify.com — via both a DNS lookup of a data-bearing label and an HTTPS GET whose query string carries the collected fields. The combination of a scoped @eforms/* name, implausibly high version (99.0.0 to win internal-vs-public resolution races), empty library surface, and preinstall OOB beacon is the standard shape of an internal-scope dependency-confusion attack. Any build that resolves this scope from the public registry ships internal host identity to the attacker's OOB collector on install.
The OpenSSF Package Analysis project identified '@eforms/forms-api' @ 2.0.0-SNAPSHOT (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @eforms/forms-api (7 malicious versions).
If you installed it — respond
@eforms/forms-api 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 @eforms/forms-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @eforms/forms-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.