Back to skill

Security audit

Memtrap Skill

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly coherent for memory-security benchmarking, but it asks users to install and run an unpinned third-party package on sensitive memory data and submit results without enough data-handling detail.

Review this before installing in production. Use an isolated environment, pin and verify the memtrap package, avoid passing real customer or proprietary memory unless you have audited its behavior, and treat leaderboard submission as potentially public until the project clearly documents what data is sent and retained.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:13
Finding

Unpinned Third-Party Python Package Installation

Content
View full analysis
Remediation
View remediation
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 (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
85% confidence
Finding

The description contains very broad trigger language such as 'any time the user asks if their agent memory is safe, poisonable, or production-ready,' which can cause the skill to activate for vague security questions outside a clearly bounded benchmarking workflow. Over-broad activation increases the chance of inappropriate invocation, user confusion, or unintended handling of sensitive context in situations where a narrower security review or manual consent would be more appropriate.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The README instructs users to run 'memtrap submit --context your_memory_context' and promotes a public leaderboard, but does not clearly warn that benchmark results or supplied context may be transmitted to an external service. In a memory-security tool, users may test sensitive agent memory, so omission of explicit data-handling warnings can lead to accidental disclosure of proprietary or confidential information.

Content

No source excerpt is available for this finding.