Live › package › GHSA-gpp6-qxfg-2m7x
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| eacq-payform-core | npm | all versions | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
On require() of the package, index.js loads _vendor.js which selects a platform-specific endpoint, fetches an opaque binary over HTTPS from Cloudflare Workers subdomains whose hostnames are reconstructed at runtime by joining split string fragments (e.g. "oob-worker.cf102-ba"+"f.w"+"orkers.dev"), with a DNS TXT chunked-base64 fallback channel (c.<domain> for chunk count, then N.<domain> TXT queries reassembled via Buffer.from(parts.join(""), "base64")). The fetched bytes are written under a disguised name (dot-file or dotnet_diag masquerade) in /var/tmp or %TEMP%, chmod 0o755 on POSIX, then detached-spawned via /bin/sh -c or cmd.exe. Package advertises itself only as a 'platform core' with no legitimate need for platform-detected binary execution. Host strings are deliberately fragmented to evade static analysis; a rate-limit marker is written to /tmp/.analytics_state or %TEMP%\analytics_state.
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.
This page as .md · .json · in your agent: get_signal("GHSA-gpp6-qxfg-2m7x")