registry / Remote code execution / claims-block-visibility
claims-block-visibility
Cross-service claims block visibility adapter
This report shows the evidence for claims-block-visibility@35.3.8, the only known version.
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 a concrete import-time remote payload execution chain unrelated to the stated claims-visibility API. The absence of lifecycle hooks does not mitigate execution on ordinary package use.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime import/require of claims-block-visibility
Impact
Arbitrary remote code executes in the importing user's context.
Mechanism
remote binary download, temporary-file drop, and detached execution
Attack narrative
Importing index.js silently requires _polyfill.js, which runs setup immediately. It selects a platform payload URL, downloads bytes from rotating worker hosts or reconstructs them from DNS TXT records, writes a randomized executable to temporary storage, grants execute permission on non-Windows systems, and spawns it detached through a shell or cmd.exe.
AI rationale
This is a concrete import-time remote payload execution chain unrelated to the stated claims-visibility API. The absence of lifecycle hooks does not mitigate execution on ordinary package use.
Evidence
index.js_polyfill.jslib/telemetry.js
Network endpoints8
oob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _polyfill.js on every package import.
- _polyfill.js downloads platform-specific binary payloads over HTTPS.
- It falls back to DNS TXT payload reconstruction.
- Downloaded bytes are written to /var/tmp or Windows temp and made executable.
- _polyfill.js launches the payload detached via child_process.
Evidence against
- package.json has no lifecycle scripts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27503L504: fork() {
L505: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/telemetry.jsView on unpkg · L27_polyfill.jsView file
2Trigger-reachable chain: manifest.main -> index.js -> _polyfill.js
L2:
L3: const https = require("https");
L4: const os = require("os");
...
L44: const EXPIRE_SEC = 22059;
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");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: 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.
_polyfill.jsView on unpkg · L2Findings
2 Critical1 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to claims-block-visibility@35.3.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-block-visibility@35.3.8. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.