registry / Remote code execution / fb-cards-form-no-resident-information

fb-cards-form-no-resident-information

Fb cards form no resident information provider for microservice architecture

This report shows the evidence for fb-cards-form-no-resident-information@20.4.4. 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-ai

This is concrete import-time staged payload execution, not package-aligned telemetry. The absence of lifecycle hooks does not mitigate execution whenever consumers import the package.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Any runtime require/import of the package entrypoint.

Impact

Arbitrary code execution under the importing process's user account.

Mechanism

Remote binary download/DNS staging followed by detached execution.

Attack narrative

The main entrypoint silently imports _adapter.js. On import, it fetches a platform-specific binary from obfuscated HTTPS hosts or reconstructs it from DNS TXT records, saves it to a temporary directory, marks it executable on Unix, and launches it detached via shell/cmd.

AI rationale

This is concrete import-time staged payload execution, not package-aligned telemetry. The absence of lifecycle hooks does not mitigate execution whenever consumers import the package.

Evidence

package.jsonindex.js_adapter.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>

Network endpoints8

oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagetin.dl.well1.sitetina.dl.well1.site

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js imports _adapter.js on every package import.
_adapter.js downloads platform binaries over HTTPS, with DNS TXT fallback.
_adapter.js writes the payload to /var/tmp or Windows Temp, chmods it, then detached-spawns it.
Payload hosts are obfuscated worker domains and well1.site DNS domains.
_adapter.js runs start() immediately and suppresses errors.

Evidence against

package.json has no lifecycle scripts.
No credential harvesting or exfiltration code was confirmed.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.9 KB of source

Source & flagged code

4 flagged

_adapter.jsView file

5const path = require("path"); L6: const https = require("https"); L7: const crypto = require("crypto"); ... L44: const STAMP_TTL = 20795; L45: const _l = (...a) => process.stderr.write(""); L46: ... L57: const isWin = _p("platform") === "win32"; L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L88: try { L89: require("dns").resolveTxt(d, (e, rr) => { L90: if (e || !rr || !rr.length) return r("");

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_adapter.jsView on unpkg · L5

5Trigger-reachable chain: manifest.main -> index.js -> _adapter.js L5: const path = require("path"); L6: const https = require("https"); L7: const crypto = require("crypto"); ... L44: const STAMP_TTL = 20795; L45: const _l = (...a) => process.stderr.write(""); L46: ... L57: const isWin = _p("platform") === "win32"; L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L88: try { L89: require("dns").resolveTxt(d, (e, rr) => { L90: 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.

_adapter.jsView on unpkg · L5

116try { L117: const cp = require("child_process"); L118: if (isWin) {

High

Child Process

Package source references child process execution.

_adapter.jsView on unpkg · L116

lib/telemetry.jsView file

•matchType = normalized_sha256 matchedPackage = twork-products-taiga2-products-mobile@20.6.6 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]: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

Source & flagged code

4 flagged · loading source

_adapter.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_adapter.jsView on unpkg · L5

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

_adapter.jsView on unpkg · L5

Findings

2 Critical2 High2 Medium1 Low

CriticalDownload Execute_adapter.js

CriticalTrigger Reachable Dangerous Capability_adapter.js

HighChild Process_adapter.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

LowFilesystem

Affected versions and remediation

This report applies to fb-cards-form-no-resident-information@20.4.4.

The versions list below shows the verdict for each recorded version.

Avoid installing fb-cards-form-no-resident-information@20.4.4. 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: 2026-08-20 01:15:13.179Z (UTC).

Source advisory published: 2026-08-05 09:09:00.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 19, 2026, 3:40 PM 20.4.4shownMaliciousRemote Code ExecutionBlockPublishedAug 2, 2026, 9:38 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages