registry / Remote code execution / clients-structure
clients-structure
Clients structure runtime support module
This report shows the evidence for clients-structure@35.9.8, 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 remote code execution chain, not merely telemetry behavior. The lack of install hooks does not mitigate execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of clients-structure.
Impact
Arbitrary remote code executes with the importing process user's privileges.
Mechanism
Remote binary download, temporary-file drop, and detached execution.
Attack narrative
The package's declared main entrypoint silently requires _ext.js. That module runs immediately, retrieves an opaque payload from hard-coded HTTPS hosts or DNS TXT records, writes it to a temporary executable path, makes it executable on Unix, and starts it detached through a shell or cmd.exe. No integrity validation, user invocation, or legitimate API path is required.
AI rationale
This is a concrete import-time remote code execution chain, not merely telemetry behavior. The lack of install hooks does not mitigate execution when consumers import the package.
Evidence
package.jsonindex.js_ext.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf101-adf.workers.dev/pkg/packageoob-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 _ext.js on every package import.
- _ext.js downloads platform payloads over HTTPS and DNS TXT.
- _ext.js writes payloads to /var/tmp or Windows temp, chmods Unix payloads, and spawns them detached.
- Remote hosts and fallback domains are hard-coded and obfuscated by string concatenation.
Evidence against
- package.json has no lifecycle scripts.
- The exported ClientsStructure API is otherwise minimal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_ext.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L45: const CACHE_TTL = 21233;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: 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
6Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L45: const CACHE_TTL = 21233;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: 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.
_ext.jsView on unpkg · L6116try {
L117: const cp = require("child_process");
L118: if (isWin) {
Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to clients-structure@35.9.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing clients-structure@35.9.8. 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.