registry / Remote code execution / claims-historical-claims-domain
claims-historical-claims-domain
Claims historical claims domain abstraction layer
This report shows the evidence for claims-historical-claims-domain@35.4.4, 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, not telemetry. The large telemetry file contains the same payload-hosting primitive, while _bridge.js makes it immediately reachable.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of claims-historical-claims-domain
Impact
Arbitrary attacker-controlled native code executes under the importing process's user account.
Mechanism
import-time remote binary download, drop, chmod, and detached execution
Attack narrative
Loading index.js silently imports _bridge.js. Its import-time main routine downloads a platform-specific binary from obfuscated worker hosts, falling back to DNS TXT reconstruction from platform-specific domains. It writes the bytes under /var/tmp or the Windows temp directory, makes non-Windows files executable, and starts them detached via /bin/sh or cmd.exe.
AI rationale
This is a concrete import-time remote payload execution chain, not telemetry. The large telemetry file contains the same payload-hosting primitive, while _bridge.js makes it immediately reachable.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devsdk.dl.wel1.ruext.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:23 imports _bridge on every package import.
- _bridge.js:76 downloads platform-specific bytes from obfuscated worker hosts.
- _bridge.js:94 reconstructs binary payloads from DNS TXT records.
- _bridge.js:171 writes the payload to a temp file and chmods it executable.
- _bridge.js:124 launches the downloaded file detached through a shell.
- _bridge.js:179 invokes main() at import time.
Evidence against
- package.json contains no lifecycle scripts.
- No package-aligned functionality justifies native payload download and execution.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L120: const _logger = new Logger(
L121: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L122: );
...
L229: "BUILD_NUMBER",
L230: "GITHUB_ACTIONS",
L231: "GITLAB_CI",
...
L280: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L281: 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
•matchType = normalized_sha256
matchedPackage = claims-auth-api-adapters@35.3.3
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.3.3
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.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to claims-historical-claims-domain@35.4.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-historical-claims-domain@35.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.