registry / Remote code execution / claims-payout-offer-api
claims-payout-offer-api
REST client wrapper
This report shows the evidence for claims-payout-offer-api@35.7.6, 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 payload execution chain unrelated to the stated REST-client purpose. The absence of npm lifecycle hooks does not mitigate the reachable runtime execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of claims-payout-offer-api.
Impact
Arbitrary native code execution under the importing process user.
Mechanism
Remote binary download and detached execution.
Attack narrative
Requiring index.js silently loads _polyfill.js. On import, it selects a platform payload, fetches it from obfuscated external hosts or reconstructs it from DNS TXT records, writes it to a temporary executable path, marks it executable on Unix, and launches it detached through a shell or cmd.exe.
AI rationale
This is an import-time remote payload execution chain unrelated to the stated REST-client purpose. The absence of npm lifecycle hooks does not mitigate the reachable runtime execution.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf100-416.workers.devoob-worker.cf103-070.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 at module load.
- _polyfill.js fetches platform binaries from worker hosts or DNS TXT records.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, and spawned detached.
- No hash/signature verification is performed before execution.
Evidence against
- package.json has no lifecycle scripts.
- The documented API in index.js is a minimal client wrapper.
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: );
...
L225: "BUILD_NUMBER",
L226: "GITHUB_ACTIONS",
L227: "GITLAB_CI",
...
L276: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L277: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27491L492: fork() {
L493: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = claims-api-clients-shared@35.1.9
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.1.9
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_polyfill.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-payout-offer-api@35.7.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-payout-offer-api@35.7.6. 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.