dshost-plugin@0.1.13
Official remote cloud relay plugin for DSHost (dshost.me): securely access your dsh Web UI from anywhere
AI Security Review
scanned 29d ago · by lpm-firewall-aiScripts are pack-time only, and the relay starts from the host apply entry after a user token is supplied. Disk collection, system metadata, and artifact reads stay inside that configured remote-access session rather than an install-time or hidden exfiltration chain.
Decision evidence
public snapshot- package.json only defines prepack and prepare, both invoking scripts/prepack.mjs. There is no preinstall, install, or postinstall hook.
- The relay WebSocket opens only from startAgent after a token is present. A missing token returns a no-op stop function.
- The only child process is execFileSync of df with the fixed argument list -kPT, used to inventory disks.
- lib/index.js starts the agent from the host apply() call, using the configured token and relay URL, defaulting to the placeholder wss://relay.example.com/agent.
- After registration, a relay http:request to /api/host.artifact can read a caller-supplied text path, including .env, and send the bytes back on that same WebSocket.
- On connect the agent reports hostname, address, disk, and installed-plugin metadata to the configured relay.
Source & flagged code
6 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
lib/core.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to dshost-plugin@0.1.13.
See all versions of dshost-plugin for other recorded verdicts.
- Review the evidence and your use of dshost-plugin@0.1.13 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.