Security audit

Calendar Sync

Security checks across malware telemetry and agentic risk

Overview

This is a simple calendar-sync skill whose sensitive calendar and OAuth behaviors are disclosed and aligned with its purpose, but users should handle deletes and credentials carefully.

Before installing, inspect any referenced calendar.py implementation if provided separately, use the narrowest calendar permissions available, protect OAuth secrets, and manually confirm the target account, calendar, event ID, and event details before creating, editing, or deleting events.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Vague Triggers

Medium

Confidence: 90% confidence
Finding: The skill’s 'When to Use' guidance is broad and does not define clear safety boundaries, approval requirements, or provider-specific constraints before taking actions on a user’s calendar. In an agent setting, vague invocation criteria can cause the skill to be triggered for sensitive scheduling tasks without sufficient confirmation, increasing the risk of unintended event creation, modification, or deletion.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The skill advertises delete/edit calendar capabilities but provides no warning, confirmation flow, or rollback guidance for destructive actions. In practice, an agent could remove events based on ambiguous user input or context, causing loss of important appointments, missed meetings, or business disruption across synchronized providers.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The configuration section instructs users to export OAuth client secrets and redirect URIs without any warning about secure storage, secret exposure, or avoiding logs/history leakage. This is risky because developers may place secrets in shell history, shared environments, screenshots, or insecure local setups, which can lead to unauthorized calendar API access.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.