registry / Remote code execution / claims-handle-api-response
claims-handle-api-response
API client bindings
This report shows the evidence for claims-handle-api-response@35.4.9, 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 an import-time remote code execution chain unrelated to the stated API-client purpose. The lack of an npm lifecycle hook does not mitigate execution on ordinary package import.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime import/require of claims-handle-api-response.
Impact
Arbitrary attacker-controlled native code can execute under the importing process's user account.
Mechanism
remote binary download/DNS payload recovery followed by detached execution
Attack narrative
The main entrypoint silently loads setup.js. That module fetches a platform-specific payload from concealed HTTPS hosts, falls back to base64 data retrieved through DNS TXT records, writes the result under a randomized temporary filename, grants execute permission on non-Windows systems, and launches it detached through a shell or cmd.exe.
AI rationale
This is an import-time remote code execution chain unrelated to the stated API-client purpose. The lack of an npm lifecycle hook does not mitigate execution on ordinary package import.
Evidence
index.jssetup.jslib/telemetry.jspackage.json
Network endpoints8
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagesdk.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:23 imports setup.js on every package import.
- setup.js:72-86 downloads binary data over HTTPS from obfuscated worker hosts.
- setup.js:90-115 reconstructs a fallback payload from DNS TXT records.
- setup.js:167-172 writes the payload to /var/tmp or Windows Temp, chmods it, then launches it detached.
- setup.js:22-42 hides download and DNS resolver hostnames through string concatenation.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent control-surface writes were found.
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");
...
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 · L27498L499: fork() {
L500: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = nxify-unic@20.3.2
matchedPath = lib/telemetry.js
matchedIdentity = npm:bnhpZnktdW5pYw:20.3.2
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 Capabilitysetup.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-handle-api-response@35.4.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-handle-api-response@35.4.9. 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.