registry / Remote code execution / claims-person-domain
claims-person-domain
Shared claims person domain library for backend integration
This report shows the evidence for claims-person-domain@35.5.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 a concrete import-time staged payload loader and remote executor, unrelated to the advertised claims-domain API. The absence of install hooks does not reduce the runtime RCE exposure.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary remote code execution under the importing process user.
Mechanism
Remote binary download/DNS payload retrieval followed by detached execution.
Attack narrative
The package entrypoint suppresses errors while importing _support.js, whose top-level start() runs on every normal package import unless opt-out variables are set. It selects a platform payload, downloads it from rotating external hosts or reconstructs it from DNS TXT records, saves it under a disguised temporary filename, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe.
AI rationale
This is a concrete import-time staged payload loader and remote executor, unrelated to the advertised claims-domain API. The absence of install hooks does not reduce the runtime RCE exposure.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf99-9b3.workers.devsdk.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 _support.js automatically on package import.
- _support.js downloads platform binaries from rotated Workers hosts.
- It falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to temp, made executable, and detached via shell/cmd.
- No lifecycle hook is needed: ordinary require() triggers the chain.
Evidence against
- package.json has no lifecycle scripts.
- The visible domain API itself is minimal and does not expose this behavior.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_support.jsView file
3const path = require("path");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L43: const STAMP_TTL = 22071;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _support.js
L3: const path = require("path");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L43: const STAMP_TTL = 22071;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_support.jsView on unpkg · L3Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to claims-person-domain@35.5.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-person-domain@35.5.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.