registry / Remote code execution / pfa-errors
pfa-errors
Internal pfa errors module for platform services
This report shows the evidence for pfa-errors@20.4.9. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, 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-aiThis is an import-time, unsigned remote native-payload execution chain unrelated to the documented error-module API. The lack of lifecycle hooks does not mitigate the reachable runtime RCE.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of pfa-errors.
Impact
Unconsented arbitrary native code execution in the importing user's environment.
Mechanism
remote payload download, drop, permission change, and detached execution
Attack narrative
At package import, index.js suppresses errors while requiring _runtime.js. That module contacts obfuscated worker hosts for a platform-specific binary, falls back to DNS TXT records containing base64 data, drops the result under a temporary filename, makes it executable on non-Windows systems, and launches it through a detached shell or cmd.exe process.
AI rationale
This is an import-time, unsigned remote native-payload execution chain unrelated to the documented error-module API. The lack of lifecycle hooks does not mitigate the reachable runtime RCE.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagetin.dl.well1.sitetina.dl.well1.siteldr.dl.well1.site
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _runtime.js on every package import.
- _runtime.js downloads platform binaries over HTTPS or DNS TXT.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, and detached-spawned.
- Remote hosts and DNS payload domains are obfuscated by string concatenation.
- No user-facing API requires or documents this runtime behavior.
Evidence against
- package.json has no lifecycle scripts.
- index.js otherwise exposes a small error-object API.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_runtime.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L43: const MAX_AGE = 20633;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L54: const isWin = _p("platform") === "win32";
L55: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L56: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L43: const MAX_AGE = 20633;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L54: const isWin = _p("platform") === "win32";
L55: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L56: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: 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.
_runtime.jsView on unpkg · L4117
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to pfa-errors@20.4.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing pfa-errors@20.4.9. 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.