Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@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)

MAL-2026-18252
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @eforms/forms-api

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

7 flagged
1.99.01.99.12.0.0-SNAPSHOT2.0.992.99.02.99.199.0.0

Indicators of compromise (SHA-256)

cbe6ac9c18c859c04807fb2bd866f2eda2b70a4aa2583096b7138ab2adc90540
e58d3810346fb211fd7ed78e8df88c774a79bb079537e10cd30baa26e5ef4740
334d1cc20f81030ef0fe0c81773bdaff1877923d618602ee7c9e0cf061666d72
3fa912f4b00d4a06e8d65e50f96d9fe283ecede2a22fc036adbfedc6d6d5ef3f
7c0ae2abc80c9c1476bbe616be8bcb075404dcd85f5c161b47f2517d2c025fab
7cf2c773e9b134db647cda4dc27ba26517b1a351a6e82ca7d1f14fc453cb4397
cdfb723707fc8aca33a9ba12128ebadfa0dc474f41a1d8d5ac72709d71e3cb66
e252cb88bb624f5846dbe43b806db42fd74b0e28a17007c73118e604ad394b16

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @eforms/forms-api (7 malicious versions).

  2. 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.

  3. 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

No. @eforms/forms-api on npm has been identified as a malicious package (versions 1.99.0, 1.99.1, 2.0.0-SNAPSHOT, 2.0.99, 2.99.0, 2.99.1, 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021707IN-MAL-2026-021745IN-MAL-2026-021746IN-MAL-2026-021748IN-MAL-2026-021750IN-MAL-2026-021749IN-MAL-2026-021747

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.

Explore