Back to skill

Security audit

Brazilian CEP using the ViaCEP API

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it says: it looks up Brazilian postal codes through ViaCEP, with only low-risk dependency and privacy considerations.

Before installing, understand that CEP queries are sent to ViaCEP over the network and that npm will resolve axios dynamically because there is no lockfile. Prefer installing in a normal isolated OpenClaw environment, and ask the publisher to pin dependencies and include a lockfile for reproducible installs.

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
package.json:7
Finding

Mutable Dependency Resolution Allows Supply-Chain Code Substitution

Content
View full analysis

Vulnerability Details

File Location: package.json:7-9
Vulnerability Type: Unpinned third-party dependency without a committed lockfile
Risk Level: Medium

Vulnerable Code

json
"dependencies": {
  "axios": "^1.6.0"
}

The project directory contains no package-lock.json, while the installation documentation instructs users to run npm install. The caret version range permits npm to select Axios releases from 1.6.0 up to, but excluding, 2.0.0, rather than installing one reviewed dependency tree reproducibly.

Technical Analysis

npm resolves the allowed package version and its transitive dependencies at installation time. Because neither the direct dependency nor the complete dependency graph is integrity-pinned by a lockfile, two installations of the same audited source can install different third-party code.

This creates a supply-chain exposure if an allowed future release, one of its transitive dependencies, or the configured package registry is compromised. npm packages can define lifecycle scripts that run during installation. Consequently, substituted dependency code may execute before the skill itself is invoked.

Axios is a legitimate package, and the audited files do not demonstrate that its current release is malicious. The issue is the project's inability to guarantee that users install the same dependency code that was reviewed.

Attack Path

  1. An attacker compromises an npm publisher, an allowed future package release, a transitive dependency, or the registry used by the victim.
  2. The attacker publishes or serves a malicious version that satisfies the ^1.6.0 constraint.
  3. A user follows the documented installation procedure and runs npm install.
  4. With no lockfile fixing package versions and integrity hashes, npm resolves the attacker-controlled package or dependency.
  5. Malicious lifecycle scripts may execute during installation. Otherwise, malicious module co ...[truncated 504 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin Axios to a specifically reviewed version instead of using a mutable caret range:
    json
    "dependencies": {
      "axios": "1.6.0"
    }
    
  2. Generate and commit package-lock.json so direct and transitive package versions and integrity hashes are recorded.
  3. Update installation instructions to use npm ci rather than npm install for reproducible deployment.
  4. Perform dependency updates through a controlled review process that checks release changes, lockfile differences, provenance, and security advisories.
  5. Where compatible with deployment requirements, install with lifecycle scripts disabled:
    bash
    npm ci --ignore-scripts
    
  6. Run dependency installation and the skill under a dedicated, least-privileged account or isolated container with restricted filesystem and network access.
  7. Use a trusted registry and enforce package provenance or organizational registry policies where available.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill sends a user-supplied CEP to the third-party ViaCEP service, which is a real data-flow/privacy issue even though the input is only a postal code. While a CEP is not highly sensitive in most cases, transmitting user input to an external service without clear disclosure or consent can expose location-related information and may violate privacy expectations or platform policies.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The dependency is specified with a caret range (^1.6.0), which allows newer minor and patch releases to be installed without explicit review. This weakens supply-chain control and can result in inconsistent builds or accidental adoption of a vulnerable or malicious upstream release.

Content

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

json
"author": "Guilherme Funchal",
    "license": "MIT",
    "dependencies": {
      "axios": "^1.6.0"
    }
}

Unverifiable Dependency: axios has 16 known advisory(ies) (CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +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
83% confidence
Finding

The manifest uses an unpinned axios dependency even though the package family has multiple known advisories, so the actual installed version cannot be confidently assessed from this file alone. In a network-facing skill that performs external API requests, a vulnerable axios release could expose the skill to issues such as SSRF, request manipulation, or other client-side transport weaknesses depending on the resolved version.

Content

No source excerpt is available for this finding.