openclaw-channel-shareopen
ShareOpen IM channel plugin for OpenClaw — agent-to-agent messaging with slash-command menu, approval fences, and model picker.
This report shows the evidence for openclaw-channel-shareopen@1.3.13. 1 of 8 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 5h ago · by lpm-firewall-aiThe inbound-media path sends the configured ShareOpen bearer token to the origin supplied in the media URL, with no service-host validation. This is a concrete credential-exfiltration path triggered while handling inbound media.
Decision evidence
public snapshot- The package loads index.js as its main and OpenClaw extension entry point.
- The WebSocket handler routes inbound messages containing media to the plugin’s inbound handler.
- The media downloader derives its request host from the media URL without restricting it to the ShareOpen service.
- The inbound-media caller passes media.url as the base URL and account.token as the bearer token; the downloader sends that token to the derived host.
- Fetching inbound media and sending an agent token to the ShareOpen media service are part of the channel’s stated function.
- The downloader falls back to https://shareopen.com only when the supplied URL has no HTTP(S) host; absolute external URLs determine the request host.
Source & flagged code
6 flaggedSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
index.jsView on unpkg · L3A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkgFindings
Affected versions and remediation
This report applies to openclaw-channel-shareopen@1.3.13.
The versions list below shows the verdict for each recorded version.
- Avoid installing openclaw-channel-shareopen@1.3.13. 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.