Iobroker Simple Api
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill is transparent about being an ioBroker controller, but it gives the agent broad smart-home write/delete authority and JavaScript execution capability that should be reviewed carefully before use.
Install only if you intentionally want OpenClaw to control ioBroker. Before use, verify the ioBroker URL, use a restricted account, avoid exposing Basic Auth over untrusted networks, and require manual approval for write, delete, bulk, scene, and exec/eval actions.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked incorrectly or by an over-eager agent, it could change devices, alter states, affect automations, or operate parts of the smart home unintentionally.
The skill exposes broad smart-home and ioBroker control, including writes and script execution, without artifact-visible allowlists, scoped device limits, or approval gates.
Full access to ioBroker via the simple-api adapter. Read states, objects, historical data, write to states, execute JavaScript, and monitor your smart home.
Use only with a trusted ioBroker instance, require explicit human confirmation for writes/deletes/bulk actions, and restrict the ioBroker account or adapter to the minimum states needed.
A mistaken or manipulated command could run automation code inside ioBroker, potentially changing devices, scripts, or system behavior.
The skill can send arbitrary JavaScript to ioBroker's exec endpoint. This is documented and purpose-aligned, but it is a powerful escape-hatch capability.
async function executeScript(code) { const url = buildUrl('exec', { script: code }); return makeRequest(url.toString()); }Disable or remove exec/eval if not required, or enforce a separate confirmation and allowlist for any script execution.
Whoever can invoke the skill can use the configured ioBroker access level; over-privileged credentials could allow broad changes to the smart-home system.
The skill reads ioBroker credentials from OpenClaw config and sends them as Basic Auth to the configured ioBroker endpoint. This is expected for the integration, but it is sensitive authority.
username: IOBROKER_CONFIG?.username || '', password: IOBROKER_CONFIG?.password || ''; requestOptions.headers['Authorization'] = 'Basic ' + auth;
Use a dedicated least-privilege ioBroker user, prefer HTTPS or a trusted local network, and keep the configured URL under user control.
If dependencies are installed, the resolved package version could change over time, making exact provenance harder to verify.
The package declares a floating dependency version. No install script or remote code download is shown, but dependency pinning would improve reviewability.
"dependencies": { "ws": "^8.14.0" }Pin dependencies with a lockfile and publish a verifiable source repository/homepage.