Todolist Md Clawdbot Copy

Security checks across malware telemetry and agentic risk

Overview

The skill mostly matches its todo-file purpose, but it asks for broad persistent Google Drive access and uses local credential/command handling that users should review before installing.

Install only if you are comfortable granting persistent Google Drive access to this skill. Prefer a dedicated Drive folder/account, verify the gog/OAuth setup, back up todo files, review changes before write-back, and revoke or delete stored tokens when you stop using it.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

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.

#
ASI03: Identity and Privilege Abuse
High
What this means

If approved, the skill can retain broad Google Drive access after the immediate task and use that access to read or update Drive content.

Why it was flagged

The script requests full Google Drive OAuth scope and stores an offline refresh token by default, giving persistent Drive authority that is broader than a single todo file.

Skill content
const refreshTokenFile = args.refreshTokenFile || process.env.REFRESH_TOKEN_FILE || '/root/clawd/.secrets/todolist_drive_oauth.json'; ... const scopes = ['https://www.googleapis.com/auth/drive']; ... refresh_token: tokens.refresh_token,
Recommendation

Use a dedicated Google account or folder where possible, prefer narrower Drive scopes if supported, keep the token file private, and revoke the OAuth grant when no longer needed.

#
ASI03: Identity and Privilege Abuse
Medium
What this means

Local Google/gog credentials could be exposed to the runtime environment or other local process observers, and the skill depends on account-level Drive access.

Why it was flagged

The folder helper reads a local gog secret file and places the keyring password into a sudo/env command invocation, which is sensitive local credential handling not reflected in the registry metadata.

Skill content
const envFile = '/root/clawd/.secrets/gog.env'; ... `GOG_KEYRING_PASSWORD=${pw}`, ... const raw = execFileSync(cmd[0], cmd.slice(1), { encoding: 'utf8' });
Recommendation

Avoid passing secrets as command arguments, run the skill in an isolated environment, and verify exactly which gog account and Drive permissions will be used.

#
ASI02: Tool Misuse and Exploitation
Low
What this means

A misconfigured gog binary or environment could cause unexpected local command behavior.

Why it was flagged

The script executes a local Drive CLI command with array arguments, which is purpose-aligned but still gives the skill local command-execution behavior.

Skill content
const cmd = ['sudo','-u','ubuntu','-H','env', ... gogBin, 'drive','ls','--parent', folderId,'--json']; const raw = execFileSync(cmd[0], cmd.slice(1), { encoding: 'utf8' });
Recommendation

Confirm the gog binary path is trusted and that the command is run only in a controlled environment.

#
ASI08: Cascading Failures
Medium
What this means

Multiple Drive Markdown files could be changed in one run if the chosen root folder is broad.

Why it was flagged

The Drive folder runner is intended to process multiple Markdown files under a root and write results back, so a too-broad root or bad suggestion could affect many todo files.

Skill content
lists all `.md` under a folder, detects changes via state file, downloads only changed files, and writes back a `` block under a dedicated section title.
Recommendation

Start with a small dedicated folder, use include/exclude config and dry runs where available, and keep backups or Drive revision history enabled.

#
ASI06: Memory and Context Poisoning
Low
What this means

Personal or work todo content may remain on local disk after the skill runs.

Why it was flagged

Downloaded Drive todo content is saved to a local output path, which can persist private task details outside Google Drive.

Skill content
const outPath = args.out || process.env.OUT_PATH || `outputs/todolist-md/${fileId}.md`; ... atomicWriteFileSync(outPath, text);
Recommendation

Store outputs in a private directory, clean up local copies when finished, and avoid using the skill on highly sensitive files unless necessary.

#
ASI04: Agentic Supply Chain Vulnerabilities
Low
What this means

Users have less assurance about where the scripts came from and what runtime dependencies are required.

Why it was flagged

The registry provenance and install contract are incomplete even though runnable helper scripts are included.

Skill content
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill; Code file presence: 3 code file(s)
Recommendation

Review the included scripts before use and install dependencies such as gog only from trusted sources.