Back to skill

Security audit

marknative

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Markdown-to-PNG/SVG helper, with a normal but mutable npm dependency install users should treat cautiously.

Before installing, confirm you trust the npm package and consider pinning `marknative` to a reviewed version or installing in a restricted project environment. Non-Chinese users may need the README or translation to follow the full runtime instructions.

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:20
Finding

Unpinned Third-Party npm Package Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 20-30
Vulnerability Type: Unpinned and mutable third-party dependency installation
Risk Level: Medium

markdown
## 先决条件

```bash
npm ls marknative skia-canvas

如果没装:

bash
npm install marknative
text

### Technical Analysis

The Skill instructs the agent or user to install `marknative` without specifying an exact version. The project does not include a `package.json`, lockfile, integrity metadata, checksum, or documented source revision that would make the installed package and its transitive dependency graph reproducible.

Running `npm install marknative` resolves mutable content from the npm registry at installation time. If the package, its maintainer account, the registry resolution process, or a transitive dependency is compromised, npm could install attacker-controlled content. npm installation can also execute package lifecycle scripts, allowing malicious code to run before the package is explicitly imported.

This finding does not establish that `marknative` or `skia-canvas` is malicious. The risk arises from the instruction to retrieve and install an unpinned dependency whose effective contents may change after the Skill has been reviewed.

### Attack Path

1. The Skill is invoked in an environment where `marknative` is not installed.
2. The dependency check using `npm ls marknative skia-canvas` reports that the required package is absent.
3. Following the Skill instructions, the agent or user runs `npm install marknative`.
4. npm resolves the current package release and its transitive dependencies from the registry without a project lockfile or an audited version constraint.
5. If any resolved package has been compromised, attacker-controlled lifecycle scripts may execute during installation, or malicious code may execute when `renderMarkdown` is imported or called.
6. The payload runs with the privil
...[truncated 710 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin marknative to a specifically reviewed version rather than resolving the latest release:
    bash
    npm install --save-exact marknative@<audited-version>
    
  2. Add a project manifest and committed lockfile containing registry integrity hashes.
  3. Use npm ci in automated or reproducible environments so installation fails when the manifest and lockfile differ.
  4. Document the verified npm package name, publisher, source repository, and audited release to reduce dependency-confusion and package-identity risks.
  5. Review direct and transitive dependencies before updating the pinned version.
  6. Where package lifecycle scripts are not required, install with:
    bash
    npm ci --ignore-scripts
    
    If native dependencies require lifecycle scripts, execute installation in a restricted environment with minimal filesystem permissions, no unnecessary credentials, and controlled network access.
  7. Run dependency vulnerability and provenance checks as part of updates, while treating automated audit output as supplemental rather than a replacement for source review.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (1)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The natural-language content of the skill is presented only in Chinese, which effectively forces a specific language on users. The policy allows locale constraints only when they are explicitly justified or when the user is given a choice, neither of which is present here.

Content

No source excerpt is available for this finding.