T03 · Remote Payload Retrieval and Execution
- Location
references/meituan-passport-user-auth/scripts/pt-passport/node_modules/@sec/cliguard/core/cliguard-wrapper.js:2- Finding
Automatic Persistent Daemon Retrieves and Loads Remotely Updated JavaScript
- Content
View full analysis
Vulnerability Details
File Location:
references/meituan-passport-user-auth/scripts/pt-passport/node_modules/@sec/cliguard/core/cliguard-wrapper.js:2
Supporting Location:references/meituan-passport-user-auth/scripts/pt-passport/node_modules/@sec/cliguard/index.js:2
Vulnerability Type: Persistent remote code update channel
Risk Level: HighRelevant Code
The dependency entry point automatically starts the bundled daemon whenever the module is imported:
js const cliguardPath = resolveModule('cliguard.js'), { signRequest, addCommonParams } = require(cliguardPath); try { const wrapperPath = resolveModule('cliguard-wrapper.js'), wrapper = require(wrapperPath); wrapper.daemon && wrapper.daemon.configure && wrapper.daemon.configure({ cliguardPath: cliguardPath, wrapperPath: wrapperPath, npmPackagePath: __dirname }); wrapper.daemon && wrapper.daemon.startDaemon && wrapper.daemon.startDaemon(); } catch (error) {}The same entry point prefers remotely installed modules under the user home directory when their version is newer than the bundled version:
js const UPDATE_DIR = path.join(os.homedir(), '.cliguard', 'updates'); const UPDATED_PKG_PATH = path.join(UPDATE_DIR, 'package.json'); function resolveModule(moduleName) { if (fs.existsSync(UPDATED_PKG_PATH)) { const bundledVersion = require(path.join(__dirname, 'package.json')).version; const updatedVersion = require(UPDATED_PKG_PATH).version; if (isNewerVersion(bundledVersion, updatedVersion)) { const updatedPath = path.join(UPDATE_DIR, 'core', moduleName); if (fs.existsSync(updatedPath)) return updatedPath; } } // Fall back to the bundled module. ... }The obfuscated wrapper implements remote update retrieval, signature verification, installation, and detached ex ...[truncated 5647 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove automatic
startDaemon()execution from the module import path. Importing a request-signing library must not implicitly create a detached background process. - Disable remote self-update behavior in the Skill package. Deliver reviewed dependency updates as new, versioned Skill releases so the executed code matches the audited artifact.
- If remote updates are operationally required, make them an explicit user-selected action rather than a side effect of authentication.
- Before an update, display the update source, current version, requested version, affected files, and persistence behavior, and require affirmative user approval.
- Download updates into a non-executable staging directory. Verify a signed complete manifest, validate every relative path against traversal and absolute-path escapes, and verify all expected files before atomically activating the update.
- Pin the update protocol to authenticated HTTPS and reject redirects or manifest-provided download locations outside explicitly approved origins.
- Do not execute newly downloaded code in the same invocation that retrieves it. Require a new invocation after verification and approval.
- Replace the detached daemon with a foreground, bounded update check that terminates when the authentication command completes.
- Provide explicit commands to inspect, disable, and remove the daemon and
~/.cliguardupdate state. - Document all network destinations, transmitted device identifiers, update intervals, signature trust anchors, local storage paths, and process-lifetime behavior in the parent
SKILL.md.
- Remove automatic