Security audit
Security checks for vulnerabilities and agentic risk
This skill is a read-only Polymarket data helper with disclosed public API calls and optional local watchlist state.
Install only if you are comfortable with the skill making public HTTP requests to Polymarket and creating a local ~/.openclaw/state directory for watchlists. Consider asking the publisher to remove or update the unused pinned requests dependency and to add explicit permission metadata for the two Polymarket domains.
The skill explicitly describes live HTTP access to public Gamma and CLOB APIs but does not declare any tool scope such as permissions or allowed-tools. That mismatch weakens security boundaries and user transparency, because a host may permit undeclared network activity or reviewers may underestimate the skill's external communication surface.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
|-------|----------|
| "Couldn't reach Polymarket" | Retry in 1 minute; check internet |
| "No markets found for..." | Try broader search term; check spelling |
| "No watchlist configured" | Add watchlist to config.yaml or create ~/.openclaw/state/polymarket_watchlist.json |
| Cached data looks stale | Cache TTL is 2 minutes; wait or restart service |
| CLOB midpoint missing | Market may not have CLOB tokens yet (new markets) |
The dependency is pinned to requests 2.32.5, and the supplied advisory indicates versions prior to 2.33.0 are affected by an insecure temporary file reuse issue in extract_zipped_paths(). Even in a read-only market data skill, shipping a known-vulnerable version is risky because vulnerable utility paths may still be reachable directly or indirectly by current or future code changes, and dependency-level flaws can become exploitable if attacker-controlled archives or paths are ever processed.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
"""Check odds on your watchlist markets."""
slugs = WATCHLIST
if not slugs:
return "❌ No watchlist configured. Create ~/.openclaw/state/polymarket_watchlist.json with market slugs."
lines = ["👀 Polymarket Watchlist", ""]
This markdown file includes multiple curl examples to public Polymarket endpoints and later notes that requests must include a User-Agent header for logging/abuse detection. The document does not provide an explicit warning that using the skill or its examples will send request metadata to an external service, which is a privacy-relevant behavior for markdown under the missing-user-warnings rule.
The manifest and module docstring emphasize a read-only Polymarket interface, which accurately describes the network behavior, but the code also manages local state by creating ~/.openclaw/state and loading a watchlist from disk. That local filesystem statefulness is broader than a purely read-only browsing interface as described, even though it does not modify Polymarket data.
No suspicious patterns detected.