Loading npm security reports…

pfa-errors@20.4.9: Malicious npm security report (Block) | LPM Firewall

registry / pfa-errors / 20.4.9

pfa-errors@20.4.9

Internal pfa errors module for platform services

AI Security Review

scanned 12d ago · by lpm-firewall-ai

Importing the package silently runs a remote binary loader. It fetches an unsigned platform payload, writes it to a temporary directory, and launches it detached.

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.

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/package

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 · L4

4Trigger-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 · L4

117try { L118: const cp = require("child_process"); L119: if (isWin) {

High

Child Process

Package source references child process execution.

_runtime.jsView on unpkg · L117

lib/telemetry.jsView file

•matchType = normalized_sha256 matchedPackage = prokit-core@20.6.6 matchedPath = lib/telemetry.js matchedIdentity = npm:cHJva2l0LWNvcmU:20.6.6 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.jsView on unpkg