Back to skill

Security audit

Near Qr Skill

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local QR-code utility for NEAR addresses and payment requests, with ordinary dependency and publishing-tool supply-chain cautions but no hidden data access or automatic high-impact actions.

Install dependencies in a virtual environment, avoid running the publishing command unless you trust and pin the MoltHub package version, and only decode QR images from sources you trust because image parsers can have vulnerabilities. Review generated payment QR details before sharing or using them, since the skill encodes payment requests but does not verify recipient intent or submit transactions.

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 (2)

T08 · Insecure Dependencies

Warning
Location
README.md:41
Finding

Mutable npm Package Is Downloaded and Executed Through npx

Content
View full analysis
Remediation
View remediation
publish`. - Prefer installing the publishing tool from a lockfile with integrity metadata and invoking that locked local installation. - Use `npx --no-install` where practical to prevent an invocation from silently downloading an absent package. - Review the selected package release, its transitive dependencies, and lifecycle scripts before use. - Keep publishing tooling separate from the runtime installation instructions so users do not mistake it for a required operational dependency. - Run publishing tools in a restricted environment with only the minimum credentials and filesystem access needed for publication. ]]>

T08 · Insecure Dependencies

Note
Location
requirements.txt:1
Finding

Python Dependencies Are Not Reproducibly Pinned

Content
View full analysis
=7.4 Pillow>=10.0 pyzbar>=0.1.9 ``` ### Technical Analysis All Python dependencies use lower-bound-only constraints. A future installation may therefore resolve to releases that did not exist when the project was audited. The file also lacks package hashes, so it does not establish artifact integrity or a reproducible reviewed dependency set. These package names appear to be normal PyPI dependencies, and the audit found no evidence of dependency confusion, typosquatting, a malicious package, or an unsafe package index. The risk is conditional on a future upstream compromise, malicious release, or incompatible vulnerable version being selected. ### Attack Path 1. An upstream dependency project or package-publishing account is compromised, or a malicious future release is published under a permitted version. 2. A user runs `pip install -r requirements.txt`. 3. The resolver selects the compromised release because every version at or above the stated minimum is allowed. 4. Malicious installation or runtime code executes when the dependency is installed, imported, or used by `near_qr.py`. 5. The code runs with the permissions of the Python installation or application user. ### Impact Assessment A compromised dependency could execute arbitrary code with the installing or runtime user's privileges. This could expose files, environment variables, source code, or credentials accessible to that account. The project itself does not grant elevated privileges, create persistence, or transmit data, so the practical scope remains limited to the invoking user's permissions unless the dependency is installed by a privileged account. ]]>
Remediation
View remediation
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (6)

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · README.md (reported line 18)May include surrounding context.

text

> **Note:** Reading QR codes requires `zbar` system library.  
> macOS: `brew install zbar` · Ubuntu: `sudo apt install libzbar0`

## Quick Start

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding

The README instructs users to run npx molthub@latest publish, which fetches and executes the latest package version at runtime without pinning. If the package is compromised or a malicious update is published, users could execute attacker-controlled code on their machine during publishing.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

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.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The dependency is specified with a lower-bound only (Pillow>=10.0), which allows any future release to be installed. This weakens build reproducibility and can unexpectedly pull in a vulnerable or breaking version, especially significant here because Pillow processes image data and has a history of security advisories.

Content

Scanner excerpt · requirements.txt (reported line 2)May include surrounding context.

text
qrcode[pil]>=7.4
Pillow>=10.0
pyzbar>=0.1.9

Unverifiable Dependency: Pillow has 16 known advisory(ies) (CVE-2016-2533 (Pillow buffer overflow in ImagingPcdDecode); CVE-2023-50447 (Arbitrary Code Execution in Pillow); CVE-2021-27922 (Pillow Uncontrolled Resource Consumption) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
92% confidence
Finding

Pillow has multiple published security advisories, and because the manifest does not pin a version, there is no way to verify whether installation will select a fixed or vulnerable release. In this skill's context, that matters more than usual because Pillow is used for QR/image generation and likely image handling, an attack surface historically associated with parsing bugs, resource exhaustion, and in some versions potentially code execution.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The pyzbar dependency is also unpinned and may resolve to different versions over time, making builds non-reproducible and increasing supply-chain risk. Because this skill reads QR codes from images, a vulnerable parser/library version could expose consumers to malformed-image handling issues or dependency-level compromise.

Content

Scanner excerpt · requirements.txt (reported line 3)May include surrounding context.

text
qrcode[pil]>=7.4
Pillow>=10.0
pyzbar>=0.1.9