Security audit

Lianke Print Box

Security checks for vulnerabilities and agentic risk

Overview

This skill appears purpose-aligned for cloud printing and scanning, but it installs an unpinned third-party CLI from a mutable Git repository that will handle credentials and documents.

Install only if you trust the Lianke CLI repository and service. Treat the API key, device ID, and device key as secrets, and avoid printing or scanning sensitive documents unless you are comfortable with the cloud service, device, and network path handling that content. Prefer a pinned, reviewed CLI version before using this in a sensitive environment.

A.I.G

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:5
Finding: Unpinned Third-Party CLI Installed from a Mutable Git Repository
Content: View full analysis
Remediation: View remediation
" ``` 2. Prefer a signed, versioned release from a trusted package registry when one is available. 3. Verify release signatures, commit signatures, or published integrity hashes before installation. 4. Review the exact pinned CLI source, including its build configuration, credential storage, network destinations, file-upload behavior, and update mechanisms. 5. Update both the Skill metadata and setup instructions so they reference the same immutable version. 6. Run the CLI under a least-privileged account or sandbox with access limited to the documents and devices needed for the requested task. 7. Store API and device credentials using operating-system-backed secure storage, restrict their permissions, and provide a documented rotation and revocation process. 8. Establish a controlled dependency-update process in which each new upstream version is reviewed and repinned explicitly. ]]>

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (2)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The skill explicitly guides users to send documents to a remote cloud printing/scanning service and external device, but it does not warn that document contents and metadata may leave the local environment and be accessible to the vendor service, device operators, or compromised endpoints. In a printing/scan workflow this is a real security concern because users may submit sensitive files under the assumption the operation is local or privacy-neutral.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The setup instructions require an API key, device ID, and device key, but provide no warning that these are sensitive secrets that can enable unauthorized access to the cloud print box and related operations if leaked via shell history, logs, screenshots, or shared terminals. Because these credentials authorize remote device interaction, disclosure could let an attacker query devices, submit jobs, or access scans depending on backend permissions.
Content: No source excerpt is available for this finding.