Back to skill

Security audit

Code Review

Security checks for vulnerabilities and agentic risk

Overview

This code-review skill is purpose-aligned but can send user code or files to an external LogicArt API without a runtime consent check or tight activation scope.

Review this carefully before installing. Use it only for code you are comfortable sending to LogicArt, and avoid running it on proprietary repositories, secrets, credentials, regulated data, or files that have not been reviewed for sensitive content.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill describes code analysis workflows and external endpoints but does not clearly warn that user code or repository contents may be sent to third-party services. In a code-review context, this is especially risky because source code often contains proprietary logic, credentials, secrets, or regulated data, and users may reasonably assume analysis is local unless told otherwise.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding

The skill demonstrates network-capable behavior by sending code to an external API, but it does not declare any explicit tool scope or permissions. This creates a governance gap: users and policy systems cannot clearly see that network access is required, increasing the risk of silent data exfiltration or misuse.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrases are very broad and match common developer requests like reviewing code or finding bugs, which can cause the skill to activate in many ordinary contexts. Because the skill routes content to third-party services, overbroad activation increases the chance that sensitive code is transmitted when the user did not intend to use an external analyzer.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
96% confidence
Finding

The skill includes a concrete example of transmitting source code to an external service via HTTPS POST. External transmission is not inherently malicious, but in this context it is security-relevant because it can export sensitive source code and associated intellectual property to a third party, especially when combined with broad triggers and missing disclosure.

Content

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

Endpoint: POST https://logic.art/api/agent/analyze

bash
curl -s -X POST "https://logic.art/api/agent/analyze" \
  -H "Content-Type: application/json" \
  -d '{"code": "your code here", "language": "javascript"}'

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The script transmits user-supplied code and inferred language to a third-party service at logic.art without any explicit consent prompt, warning, or visible disclosure at runtime. In a code-review skill, this is especially risky because users may analyze proprietary source code, secrets, credentials, or internal business logic and unknowingly exfiltrate sensitive material outside their trust boundary.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.