registry / Remote code execution / claims-policy-details-domain
claims-policy-details-domain
Claims policy details domain SDK for internal consumers
This report shows the evidence for claims-policy-details-domain@35.9.3, 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-aiThe concrete import-time remote payload download and detached execution are malicious behavior, not package-aligned SDK functionality. Absence of lifecycle hooks does not mitigate the reachable import-time execution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime require/import of index.js
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
Remote binary download, DNS fallback, temporary-file drop, and detached execution
Attack narrative
The public entrypoint suppresses errors while importing _vendor.js. That module immediately runs, contacts rotating worker hosts for a platform-specific binary, falls back to DNS TXT payload reconstruction, writes the result under a misleading temporary filename, and launches it detached via cmd.exe or /bin/sh. This is an unconsented remote-code-execution chain on ordinary package import.
AI rationale
The concrete import-time remote payload download and detached execution are malicious behavior, not package-aligned SDK functionality. Absence of lifecycle hooks does not mitigate the reachable import-time execution.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.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 _vendor.js on every package import.
- _vendor.js downloads platform binaries from workers.dev hosts.
- _vendor.js can reconstruct a payload through DNS TXT records.
- _vendor.js writes and executes the downloaded payload detached.
- Payload is disguised as telemetry/cache files in temporary directories.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration writes found.
- lib/telemetry.js is not imported by the public entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_vendor.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const fs = require("fs");
...
L47: const TTL = 20461;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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 os = require("os");
L5: const https = require("https");
L6: const fs = require("fs");
...
L47: const TTL = 20461;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to claims-policy-details-domain@35.9.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-policy-details-domain@35.9.3. 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.