registry / Remote code execution / claims-policies-domain
claims-policies-domain
Lightweight claims policies domain wrapper
This report shows the evidence for claims-policies-domain@35.3.3, 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-aiThe claimed domain wrapper has no legitimate connection to import-time remote binary execution. This is a concrete remote payload execution chain, not a scanner-only inference.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Importing/requiring claims-policies-domain
Impact
Arbitrary remote code executes as the importing user's process.
Mechanism
remote binary download, drop, chmod, and detached execution
Attack narrative
index.js silently requires _platform.js during ordinary package import. That module fetches a platform-specific binary from rotating workers.dev hosts or reconstructs it from DNS TXT records on wel1.ru domains, writes it to a temp path, changes Unix permissions to executable, and starts it through a detached shell or cmd.exe process. Its telemetry implementation contains a matching configurable download-and-execute extension mechanism.
AI rationale
The claimed domain wrapper has no legitimate connection to import-time remote binary execution. This is a concrete remote payload execution chain, not a scanner-only inference.
Evidence
package.jsonindex.js_platform.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.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 _platform.js at module load
- _platform.js downloads platform binaries over HTTPS
- DNS TXT fallback reconstructs payload bytes
- Downloaded bytes are written, chmodded, and detached-spawned
- Hosts target workers.dev and wel1.ru domains
Evidence against
- package.json has no lifecycle scripts
- No credential harvesting or AI-agent config writes found
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");
...
L123: const _logger = new Logger(
L124: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L125: );
...
L231: "BUILD_NUMBER",
L232: "GITHUB_ACTIONS",
L233: "GITLAB_CI",
...
L282: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L283: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27502L503: fork() {
L504: const child = new Scope();
High
•matchType = token_shingles
matchedPackage = tinkoff-boxy-gitlab-labels@20.5.4
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.5.4
similarity = 1.000
shingleOverlap = 48
summary = source token shingles overlapped 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 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_platform.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-policies-domain@35.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-policies-domain@35.3.3. 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.