Aave Liquidation Monitor
Security checks across malware telemetry and agentic risk
Overview
This looks like a read-only Aave alerting skill, but it needs review because it runs persistent background checks and its privacy/logging claims understate where detailed position data can be stored or sent.
Before installing, be comfortable with a background job periodically querying Aave for your wallet and sending/storing alert text that may include collateral, debt, and asset details. Use a private notification channel, review log retention, and disable or remove the cron job when you no longer need monitoring.
VirusTotal
64/64 vendors flagged this skill as clean.
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.
A user may believe detailed Aave position information is never retained, when it may appear in alert text, OpenClaw history, or connected chat notifications.
This strong assurance is in tension with the implementation and cron documentation: the monitor formats collateral, debt, borrowed assets, and supplied assets into alert output, and the cron guide says alert messages/check results are logged to OpenClaw session history.
❌ **No sensitive logging** — API responses are parsed safely; position data is NOT logged
Clarify the privacy documentation to say exactly which position fields appear in alerts, console output, and session history; provide redaction or log-minimization options if possible.
Your Aave health factor and possibly position summaries may remain in OpenClaw history after the alert is sent.
The skill intentionally keeps a record of monitoring activity. Because alerts can include DeFi portfolio details, session history retention is privacy-relevant even though it is purpose-aligned.
All checks are logged to OpenClaw session history: ... Includes alert messages and check results for audit trail.
Review OpenClaw session-history retention, delete old logs if needed, and avoid enabling verbose summaries if you do not want routine position data stored.
Anyone with access to the configured chat channel may see your liquidation-risk alerts and position details.
Alert delivery through Telegram, Discord, or Slack is disclosed and purpose-aligned, but it means financial risk alerts leave the local skill context through external messaging integrations.
The skill calls OpenClaw's messaging API with just the alert text ... OpenClaw routes the message using your configured channels
Use a private messaging channel, confirm the correct channel is configured, and avoid shared workspaces for sensitive wallet monitoring.
After enabling, the skill will keep making scheduled Aave API checks and may send alerts until you disable it.
Persistent background execution is a sensitive capability, but here it is central to the stated monitoring purpose and the docs provide status, disable, and remove commands.
The skill registers a cron job that silently runs in the background and alerts you only when health factor drops below threshold.
Check the configured interval and channel after enabling, and use `/aave-monitor disable` or `/aave-monitor disable --remove` when monitoring is no longer needed.
You have less external provenance information to verify who maintains the code and how updates are produced.
The skill includes runnable Node scripts, but the registry metadata does not provide a source homepage or install specification. This is a provenance/reviewability note, not evidence of malicious behavior.
Source: unknown; Homepage: none ... No install spec — this is an instruction-only skill ... 2 code file(s)
Install only from a trusted ClawHub listing, review the included scripts before enabling persistent monitoring, and prefer versions with a public source repository.