T02 · Agent Memory Poisoning
- Location
setup.md:21- Finding
Cross-Session Behavior Modification Through Main Memory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its public-sentiment monitoring purpose, but it also tells the agent to save activation preferences into shared main memory while claiming tracking data stays local.
Review this before installing if you do not want a skill to influence future sessions. One-off sentiment checks are aligned with the skill's purpose, but ongoing monitoring should require explicit consent, clear schedule limits, and storage only in the local sentiment-analysis folder unless you knowingly opt into shared memory.
setup.md:21Cross-Session Behavior Modification Through Main Memory
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
default_timeframe: 7d
## Entities
<!-- List of tracked entities, one per line -->
<!-- Format: name | type | schedule | platforms -->
| Entity | Type | Schedule | Platforms |
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# Alert History
## Active Alerts
<!-- Alerts that haven't been acknowledged -->
### YYYY-MM-DD HH:MM — {Entity}
**Type:** negative_spike
The file claims that all tracking data stays locally on the user's machine, but later directs the agent to save information to MAIN memory across sessions. This inconsistency is dangerous because it misleads users about where their data is stored and undermines informed consent around persistence and data sharing.
The skill instructs saving user preferences to "MAIN memory" shared across sessions, which expands data persistence beyond the stated local skill scope. This creates unnecessary cross-session profiling risk and can expose user preferences to other workflows or skills without a clear need tied to sentiment monitoring.
The skill directs persistent storage of user preferences without a clear user-facing disclosure at the moment of collection and storage. Even if the data seems low sensitivity, silent persistence can accumulate behavioral preferences and monitoring choices that users did not knowingly authorize to be retained.
The instructions say to save learned entities, alert thresholds, report preferences, and platform priorities to a local file, but they do not require a contemporaneous disclosure to the user that this profiling data is being persisted. This creates a privacy and transparency issue because operational preferences and tracked interests may reveal sensitive business focus or personal interests over time.
No suspicious patterns detected.