Back to skill

Security audit

Conversation Logger

Security checks across malware telemetry and agentic risk

Overview

This skill has a coherent conversation-logging purpose, but it should be reviewed because it tells agents to silently persist and reload conversation summaries without clear consent, retention, deletion, or redaction controls.

Install only if you intentionally want local, persistent conversation memory. Before enabling it, decide where logs are stored, who can read them, how long they are kept, how to delete them, and whether secrets, credentials, customer data, or regulated information must be excluded. Consider changing the instructions so logging and prior-log loading are visible or opt-in.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (8)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The README explicitly promotes silent automatic conversation logging after each turn without mentioning consent, privacy notice, retention limits, or handling of sensitive data. In an agent skill, this can cause collection and storage of user-provided secrets, personal data, and business context without clear awareness, increasing privacy and compliance risk.

Missing User Warnings

High
Confidence
98% confidence
Finding
The skill explicitly requires silent per-turn persistence of conversation summaries with no user-visible disclosure. This creates undisclosed retention of user data and can capture sensitive project details, questions, file paths, and decisions without informed consent or clear operator awareness.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill auto-loads prior logs into context on the first turn of the day without notifying the user. Hidden context loading can reintroduce sensitive or stale data into future interactions, affecting model behavior in ways the user cannot see or reasonably anticipate.

Ssd 3

Medium
Confidence
94% confidence
Finding
The combination of silent per-turn logging and historical retrieval creates a persistent store of natural-language conversation content that may include credentials, internal plans, regulated data, or private user information. Retrieval by date or keyword increases the chance that sensitive historical content can be resurfaced and disclosed beyond the original conversational context.

Ssd 3

Medium
Confidence
97% confidence
Finding
Silent per-turn logging persists user-derived content without disclosure, increasing privacy risk and creating a durable record that may later be accessed by humans, tools, or other agents. Even if summaries are short, they still include behavioral and project context that may be sensitive.

Ssd 3

Medium
Confidence
96% confidence
Finding
The template directs the agent to store the user's core question, which may include secrets, internal plans, credentials, personal information, or regulated data. Persisting this content in project files expands exposure and may violate privacy or data-handling expectations.

Ssd 3

Medium
Confidence
94% confidence
Finding
Automatically reloading previous logs reintroduces stored user data as hidden context, which can leak prior sensitive information into new tasks or bias responses based on data the user did not explicitly provide in the current session. This is especially risky in multi-project or shared environments where boundaries may be imperfect.

Session Persistence

Medium
Category
Rogue Agent
Content
- **Auto-silent logging** — Agent writes structured summaries silently after each turn
- **Daily context continuity** — Auto-reads yesterday's log on the first turn of each day
- **Manual lookup** — On-demand retrieval of historical logs by date or keyword
- **Sub-agent support** — Spawned agents can write to the same daily log

## Quick Start
Confidence
81% confidence
Finding
write to the same daily log ## Quick Start ### 1. Place the skill file Copy `SKILL.md` to your workspace: ``` {workspace}/skills/conversation-logger/SKILL.md ``` ### 2. Create log directories ``

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Static analysis

No suspicious patterns detected.