registry / Remote code execution / claims-policies-api-adapters
claims-policies-api-adapters
REST client wrapper
This report shows the evidence for claims-policies-api-adapters@35.6.7, 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 advertised REST client wrapper. The package provides no signature, hash, or user-invoked setup boundary for the downloaded executable.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any require/import of the package main entrypoint (index.js).
Impact
Arbitrary remote code executes with the importing process's permissions.
Mechanism
remote binary download, temporary-file drop, permission change, and detached shell execution
Attack narrative
The declared main entrypoint loads _vendor.js inside a swallowed-error wrapper. That module immediately runs bootstrap, downloads a binary from obfuscated workers.dev mirrors or reconstructs one from attacker-controlled DNS TXT records, writes it to a temporary location, marks it executable on Unix, and launches it through a detached shell or cmd.exe process. The marker file only reduces repeat execution; it does not provide consent or integrity validation.
AI rationale
This is a concrete import-time remote payload execution chain unrelated to the advertised REST client wrapper. The package provides no signature, hash, or user-invoked setup boundary for the downloaded executable.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagesdk.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 at package import time.
- _vendor.js downloads platform binaries from four workers.dev hosts.
- _vendor.js falls back to DNS TXT payloads from wel1.ru domains.
- Downloaded content is written to /var/tmp or Windows Temp, chmodded, and spawned detached.
- No lifecycle hook is needed: requiring the declared main triggers bootstrap.
Evidence against
- package.json declares no lifecycle scripts.
- The public adapter class itself is minimal, but it does not prevent the import-time payload loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
3 flagged · loading source_vendor.jsView file
3const path = require("path");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L44: const TTL = 22914;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: 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
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L3: const path = require("path");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L44: const TTL = 22914;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: 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.
_vendor.jsView on unpkg · L3Findings
2 Critical1 High3 Medium2 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to claims-policies-api-adapters@35.6.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-policies-api-adapters@35.6.7. 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.