T06 · System Persistence
- Location
SKILL.md:125- Finding
Persistent Calendar Bridge User Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for a real calendar-bridge workflow, but it asks users to run unpinned external code persistently with Google Calendar credentials and leaves local calendar access under-scoped.
Review before installing. Only use this if you trust and pin the external repository revision, understand the npm dependency risk, require a strong CALENDAR_BRIDGE_API_KEY, keep the service bound to localhost, and know how to disable the systemd user service and revoke Google OAuth access.
SKILL.md:125Persistent Calendar Bridge User Service
SKILL.md:84Execution of Mutable External Source and Unverified npm Dependencies
SKILL.md:68Calendar Data API Permits Unauthenticated Local Access by Default
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
git clone https://github.com/DanielKillenberger/gcal-oauth-bridge.git cd gcal-oauth-bridge npm install cp .env.example .env
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
git clone https://github.com/DanielKillenberger/gcal-oauth-bridge.git cd gcal-oauth-bridge npm install cp .env.example .env
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.
systemctl --user enable calendar-bridge.service
systemctl --user start calendar-bridge.service
The standalone trigger "google calendar" is extremely broad and can appear in ordinary conversation, general product questions, or unrelated support requests. Because no contextual constraints are attached, it risks unintended invocation of this specific self-hosted bridge skill.
The triggers "set up calendar", "calendar auth", and "calendar access" are generic and could match many unrelated calendar configuration tasks, not specifically this local Calendar Bridge service. The file does not provide exclusion conditions or tighter scoping to distinguish when this skill should activate versus other calendar or setup workflows.
No suspicious patterns detected.