registry / Remote code execution / claims-shared
claims-shared
Pluggable claims shared interface
This report shows the evidence for claims-shared@35.7.1, 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 concrete import-time remote payload execution, not normal telemetry. The unused-looking telemetry module independently contains a similar downloader design, reinforcing intent.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of claims-shared.
Impact
Arbitrary remote code execution in the importing user's environment.
Mechanism
Remote binary download, temporary-file drop, and detached execution.
Attack narrative
On import, index.js loads _polyfill.js and suppresses errors. That module checks a temporary stamp, fetches a platform-specific payload from obfuscated worker hosts or reconstructs one from DNS TXT records, writes it to /var/tmp or the Windows temp directory, marks it executable on Unix, and starts it detached through /bin/sh or cmd.exe.
AI rationale
This is concrete import-time remote payload execution, not normal telemetry. The unused-looking telemetry module independently contains a similar downloader design, reinforcing intent.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js
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.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 on every package import.
- _polyfill.js downloads platform payloads over HTTPS.
- Downloaded bytes are written to a temporary executable path and chmodded on Unix.
- _polyfill.js launches the payload via shell/cmd in a detached process.
- DNS TXT fallback reconstructs a base64 payload.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or exfiltration was confirmed in the import path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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");
...
L117: const _logger = new Logger(
L118: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L119: );
...
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 · L27500L501: fork() {
L502: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = checkout-base-test@35.9.3
matchedPath = lib/telemetry.js
matchedIdentity = npm:Y2hlY2tvdXQtYmFzZS10ZXN0:35.9.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.jsView on unpkgFindings
2 Critical2 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/telemetry.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to claims-shared@35.7.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-shared@35.7.1. 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.