ClawHub
Back to skill

Security audit

Geoskill: Land Subsidence InSAR

Security checks for vulnerabilities and agentic risk

Overview

The skill is not malicious, but it can produce land-subsidence reports from data that is not actually displacement data, which could mislead users making hazard decisions.

Install only if you understand that bbox/AOI auto-download mode is not a reliable InSAR displacement workflow. For real subsidence assessment, use vetted displacement rasters, avoid relying on the GRD auto-download output for decisions, and pin/review dependencies before use in controlled environments.

SkillSpector

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (6)

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
The auto-download path claims to support InSAR subsidence analysis, but it fetches Sentinel-1 GRD imagery and passes it directly as a displacement raster. This is a semantic data-substitution flaw: users may trust scientifically invalid outputs as real subsidence measurements, which can drive incorrect operational or policy decisions. In this context, the danger is amplified because the script presents authoritative metrics and reports without validating that the input is an actual displacement product.

Context-Inappropriate Capability

Medium
Confidence
82% confidence
Finding
The skill can perform external network acquisition and automatically ingest downloaded data into the analysis pipeline. While not inherently malicious, this expands the trust boundary and can introduce unreviewed remote content, nondeterministic behavior, data provenance issues, and unexpected resource consumption. In a security-sensitive or reproducibility-focused environment, hidden or automatic fetching makes misuse and misinterpretation more likely.

Unpinned Dependencies

Low
Category
Supply Chain
Content
geoskill-data-fetcher>=0.2.0

# Third-party dependencies used by this skill
numpy
rasterio
Confidence
94% confidence
Finding
The dependency `numpy` is unpinned, so builds may resolve to different versions over time, including versions with known defects or breaking changes. In a supply-chain context this increases the chance of pulling a vulnerable or compromised release and makes security review and reproducibility difficult.

Unpinned Dependencies

Low
Category
Supply Chain
Content
# Third-party dependencies used by this skill
numpy
rasterio
Confidence
92% confidence
Finding
The dependency `rasterio` is unpinned, allowing environment-dependent version resolution and reducing build reproducibility. Because geospatial libraries often include native code and complex parser behavior, unpinned installs can unintentionally introduce security issues or unstable behavior.

Unpinned Dependencies

Low
Category
Supply Chain
Content
# Requirements for land-subsidence-insar
# Shared data-download library (Planetary Computer / NASA POWER / OSM)
geoskill-data-fetcher>=0.2.0

# Third-party dependencies used by this skill
numpy
Confidence
96% confidence
Finding
Using `geoskill-data-fetcher>=0.2.0` permits any newer version to be installed, including future releases that have not been reviewed for this skill. This is a supply-chain risk because a malicious, compromised, or incompatible upstream release could be pulled automatically.

Known Vulnerable Dependency: numpy — 10 advisory(ies): CVE-2014-1859 (Numpy arbitrary file write via symlink attack); CVE-2021-41495 (NumPy NULL Pointer Dereference); CVE-2021-33430 (NumPy Buffer Overflow (Disputed)) +7 more

Critical
Category
Supply Chain
Confidence
90% confidence
Finding
`numpy` is referenced without a version pin, and static analysis indicates multiple advisories exist for some NumPy releases. Without constraining the version, the installation may resolve to a vulnerable release depending on the environment or resolver state, making this a real supply-chain exposure rather than a purely theoretical issue.

Static analysis

No suspicious patterns detected.