Back to skill

Security audit

Heartbeat Checklist

Security checks for vulnerabilities and agentic risk

Overview

This heartbeat checklist is not overtly malicious, but it gives an agent broad ongoing authority to alter memory, restart services, re-enable a persistent timer, close apps/tabs, and move files without clear user approval or limits.

Install only if you want an agent to perform active system and memory maintenance. Before use, require explicit confirmation for service restarts, timer re-enablement, closing apps/tabs, moving files, and editing memory; limit log and file access to known paths and keep memory changes reviewable.

Vulnerability Patterns
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • System PersistenceInstalls backdoors, hooks, services, or scheduled tasks that survive the run
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (3)

T02 · Agent Memory Poisoning

Error
Location
SKILL.md:34
Finding

Unreviewed Persistent Agent Memory Modification

Content
View full analysis
60%**: Save summary to `memory/YYYY-MM-DD.md` ``` ```markdown - [ ] Review recent daily notes - [ ] Update MEMORY.md with distilled learnings - [ ] Remove outdated info ``` ### Technical Analysis The skill instructs the agent to summarize current-session content into persistent daily memory and subsequently incorporate selected information into `MEMORY.md`. It also authorizes removal of information considered outdated. Because recent session content may include untrusted user input, retrieved documents, or prompt-injection material, automatically persisting a summary creates a cross-session trust-boundary violation. Malicious instructions can be transformed into apparently trusted memory and influence future agent behavior. The instruction to remove outdated information can additionally erase legitimate context or security guidance without review. No validation, provenance tracking, separation of data from instructions, approval gate, or rollback mechanism is specified. ### Attack Path 1. An attacker introduces malicious or misleading instructions into content processed during a session. 2. Session context usage exceeds the stated 60% threshold. 3. The heartbeat procedure summarizes the session, including attacker-influenced content, into `memory/YYYY-MM-DD.md`. 4. A later heartbeat reviews the daily note and distills its contents into `MEMORY.md`. 5. Future sessions consume the poisoned memory as persistent context. 6. The attacker-controlled guidance continues to affect later decisions, even after the original session has ended. 7. Legitimate contradictory information may be removed under the instruction to delete outdated material. ### Impact Assessment Successful exploitation can obtain pers ...[truncated 375 chars]
Remediation
View remediation

T06 · System Persistence

Error
Location
SKILL.md:27
Finding

Automatic Re-enablement of a Persistent User Service Timer

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:17
Finding

Overbroad Access to Logs, Applications, Browser State, and User Files

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The self-healing section directs the agent to diagnose and fix issues and to restart a daemon if inactive, but provides no constraints on what may be modified or when consent is required. This creates a pathway for autonomous system changes that could alter services, mask underlying problems, or cause unintended operational impact.

Content

No source excerpt is available for this finding.

Session Persistence

Medium
Category
Rogue Agent
Confidence
82% confidence
Finding

The instruction to reenable a user systemd timer if it is inactive establishes or restores persistent background behavior on the system. Persistence-related actions are sensitive because they can survive beyond the current session, change system behavior without visibility, and be abused to maintain unauthorized long-term execution.

Content

Scanner excerpt · SKILL.md (reported line 27)May include surrounding context.

md
- [ ] Any time-sensitive opportunities?

## System Hygiene
- [ ] **Check Sentinel:** `systemctl --user is-active resource-monitor.timer` - if dead, reenable
- [ ] Close unused apps
- [ ] Clean stale browser tabs
- [ ] Move old screenshots to trash

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill instructs the agent to perform system-affecting housekeeping actions such as reenabling a user timer, closing applications, deleting screenshots, and cleaning browser tabs without requiring explicit user confirmation or defining safety boundaries. In an autonomous agent context, these actions can cause loss of user state, unintended persistence changes, or destructive cleanup on the host system.

Content

No source excerpt is available for this finding.