dingtalk-link

Security checks across malware telemetry and agentic risk

Overview

This is a straightforward setup guide for connecting OpenClaw to a DingTalk bot, with expected plugin installation and credential configuration steps.

Before installing, confirm you trust the DingTalk connector package and repository. Treat AppSecret and API keys as private credentials: do not commit ~/.openclaw/openclaw.json, avoid sharing logs or screenshots containing secrets, restrict local file access where possible, and rotate credentials if they may have been exposed.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The guide explicitly instructs users to place AppKey and AppSecret in a plaintext local config file but provides no warning about secret handling, file permissions, backups, or source-control exposure. While local configuration of credentials can be legitimate, omitting basic secret-safety guidance increases the risk that users will store long-lived credentials insecurely and leak them through logs, screenshots, backups, or accidental commits.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal