Malicious code in @eforms/forms-api (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (e58d3810346fb211fd7ed78e8df88c774a79bb079537e10cd30baa26e5ef4740) The npm package @eforms/forms-api@99.0.0 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…

Published by the source

25 Oct 2026, 06:26 UTC

Last modified by the source

29 Oct 2026, 14:30 UTC

Source last checked

30 Oct 2026, 06:15 UTC

1. Revision 3 · amended · 30 Oct 2026

   Amended from osv record MAL-2026-18252

2. Revision 2 · amended · 27 Oct 2026

   Amended from osv record MAL-2026-18252

3. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18252

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-39p9-96vf-fxjh

Advisory: Malicious code in @eforms/forms-api (npm)
IDs: GHSA-39p9-96vf-fxjh
Record: https://patchnext.com/advisories/mal-2026-18252 (revision 3, source checked 30 Oct 2026, 06:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @eforms/forms-api: affected every version

## Suggested inspection (read-only)
- `npm ls @eforms/forms-api --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @eforms/forms-api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18252 (OSV record MAL-2026-18252 lists affected ranges: npm @eforms/forms-api >=2.0.0-SNAPSHOT =99.0.0 =2.99.0 =1.99.0 =2.99.1 =1.99.1 =2.0.99 <=2.0.99)
- Verified: https://osv.dev/vulnerability/MAL-2026-18252 (OSV record MAL-2026-18252 lists affected ranges: npm @eforms/forms-api >=0)

Commands are suggestions: review each one before running it.