registry / Remote code execution / eacq-payform-core
eacq-payform-core
platform core
This report shows the evidence for eacq-payform-core@20.3.6. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.0-stage, is allowed. See all versions.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe malicious loader is reachable at import time and executes unverified remote bytes. No lifecycle hook is required for the attack to affect package consumers.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of eacq-payform-core.
Impact
Arbitrary attacker-controlled native code executes under the importing process's user account.
Mechanism
Obfuscated remote binary download, temp-file drop, chmod, and detached shell execution.
Attack narrative
On normal module import, index.js loads _vendor.js, which runs setup(). The loader contacts obfuscated worker hosts for platform-specific binary content, with DNS TXT chunk retrieval as fallback. It writes sufficient-size content to a disguised temporary executable, makes it executable on Unix, and launches it detached through /bin/sh or cmd.exe. This is a concrete remote-code-execution loader, not package-aligned telemetry.
AI rationale
The malicious loader is reachable at import time and executes unverified remote bytes. No lifecycle hook is required for the attack to affect package consumers.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports ./_vendor on every package import.
- _vendor.js immediately calls setup() without user action.
- _vendor.js downloads executable bytes from four workers.dev hosts or DNS TXT records.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, and detached-spawned.
- Payload hosts/domains are obfuscated and unrelated to the stated payment-core package.
Evidence against
- package.json has no lifecycle scripts.
- Public index.js API is otherwise a minimal inert class.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
3 flagged · loading source_vendor.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const fs = require("fs");
...
L44: const EXPIRE_SEC = 22292;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const fs = require("fs");
...
L44: const EXPIRE_SEC = 22292;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L4Findings
2 Critical1 High3 Medium2 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to eacq-payform-core@20.3.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing eacq-payform-core@20.3.6. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.