Back to skill

Security audit

Meow Finder

Security checks for vulnerabilities and agentic risk

Overview

This is a small offline CLI for searching a bundled list of AI tools, with only low-level npm supply-chain hygiene concerns.

Install only if you are comfortable with a global npm CLI package from this publisher. For stronger supply-chain assurance, prefer an exact reviewed version or a lockfile-based install path before using it in managed or sensitive environments.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (5)

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
92% confidence
Finding

The dependency is specified with a caret range, which allows newer minor/patch releases to be installed over time. That weakens build reproducibility and can unexpectedly introduce vulnerable or malicious upstream code through normal installs, though this file alone does not show active exploitation.

Content

Scanner excerpt · package.json (reported line 17)May include surrounding context.

json
"url": "https://github.com/abgohel/meow-finder"
  },
  "dependencies": {
    "commander": "^12.0.0",
    "node-fetch": "^3.3.0",
    "chalk": "^5.3.0"
  }

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The node-fetch dependency is unpinned, so installs may resolve to different releases within the allowed range. Because node-fetch has known historical advisories, leaving the version floating increases supply-chain risk and makes it impossible to verify whether deployed instances are using a safe version.

Content

Scanner excerpt · package.json (reported line 18)May include surrounding context.

json
},
  "dependencies": {
    "commander": "^12.0.0",
    "node-fetch": "^3.3.0",
    "chalk": "^5.3.0"
  }
}

Unverifiable Dependency: node-fetch has 3 known advisory(ies) (CVE-2022-0235 (node-fetch forwards secure headers to untrusted sites); CVE-2022-2596 (node-fetch Inefficient Regular Expression Complexity ); CVE-2020-15168 (The `size` option isn't honored after following a redirect in node-fetch)), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
82% confidence
Finding

The manifest does not pin node-fetch, so the actual installed version cannot be verified against known advisories. In a CLI that likely performs network requests, a vulnerable fetch library could affect request handling, header forwarding, or resource consumption depending on the resolved release.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
98% confidence
Finding

The chalk dependency is unpinned, allowing automatic resolution changes over time. Given the cited malicious-package advisory context, this creates avoidable supply-chain exposure because a future install could pick up a compromised but semver-compatible release.

Content

Scanner excerpt · package.json (reported line 19)May include surrounding context.

json
"dependencies": {
    "commander": "^12.0.0",
    "node-fetch": "^3.3.0",
    "chalk": "^5.3.0"
  }
}

Unverifiable Dependency: chalk has 1 known advisory(ies) (MAL-2025-46969 (Malicious code in chalk (npm))), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
74% confidence
Finding

Because chalk is not pinned, the project cannot prove that installed environments avoid the referenced malicious-package advisory. Even though chalk is typically a terminal-formatting library, supply-chain compromise in any runtime dependency can lead to arbitrary code execution during installation or execution.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.