Back to skill

Security audit

warapp-api

Security checks for vulnerabilities and agentic risk

Overview

The verdict is benign with medium confidence: scanners found no AIG issues and judged the flagged credential use and external API request likely consistent with the skill, but analysis was incomplete for some files.

The benign verdict is not a guarantee of safety. Consider whether you trust the skill to use your WARAPP credentials with its external API. Some files were only partially inspected, so the evidence is incomplete; review the skill's access and credential requirements before installing.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
`references/scout.mjs` (Node, no dependencies) reads the page's HTML on stdin and prints

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
anything but `scout.mjs`. Player and game names are written by other players — report them,

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
are `null`. `scout.mjs` exits `0` ok · `1` usage · `2` no HTML on stdin (the `fpx` call

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/warapp.sh (reported line 10)May include surrounding context.

sh
# Every call is POST https://war.app/API/GameFeed?GameID=<n> with the form body
# Email=<email>&APIToken=<token>. Credentials come from WARAPP_EMAIL /
# WARAPP_API_TOKEN, else from the dotenv file WARAPP_ENV_FILE (default
# ~/.config/warapp-mcp/.env — the same file warapp-mcp reads). The environment
# wins over the file. The file is parsed, never sourced, and the credentials
# live only in function-local variables: they are never exported, never put
# on curl's command line (the body goes in on stdin) and never printed — an

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: env, shell.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
70% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · scripts/warapp.sh (reported line 149)May include surrounding context.

sh
printf 'Email=%s&APIToken=%s' \
      "$(printf '%s' "$_warapp_email" | _warapp_uri)" \
      "$(printf '%s' "$_warapp_token" | _warapp_uri)" |
      curl -q --globoff --proto "$proto" --max-redirs 0 --noproxy "$noproxy" \
        -sS --fail-with-body --max-time 30 --retry 1 \
        -H 'Content-Type: application/x-www-form-urlencoded' \
        --data-binary @- \