Back to skill

Security audit

Lineage Claws

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local provenance verifier, but it overstates its cryptographic guarantees and produces proof-like outputs that are not actually signed or independently verified.

Install only if you need a project-specific MOSES lineage helper and are comfortable with it writing local OpenClaw governance/audit files. Do not treat its badge or attestation output as independent cryptographic proof, a digital signature, legal custody evidence, or a complete ledger integrity check without additional external validation.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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 (4)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/lineage.py:167
Finding

Live Ledger Verification Validates Only the Public Anchor Field

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/archival.py:175
Finding

Archival Verification Does Not Recompute Hashes from Stored Block Contents

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
scripts/lineage.py:290
Finding

Purported Signed Attestations Use a Forgeable Unkeyed Hash

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/lineage.py:21
Finding

Archival Provenance Chain Is Not Cryptographically Bound to the Lineage Anchor

Content
View full analysis
list[dict]: """Construct the archival chain from PROVENANCE_CLAIMS.""" chain = [] prev = "0" * 64 # Genesis has no predecessor for claim in PROVENANCE_CLAIMS: block = { "seq": claim["seq"], "claim": claim["claim"], "claim_type": claim["claim_type"], "external_ref": claim["external_ref"], "author": claim["author"], "previous_hash": prev, } h = block_hash(block) block["hash"] = h chain.append(block) prev = h return chain ``` ### Technical Analysis The documented model claims a three-layer chain: ```text archival chain -> archival head -> anchor -> live ledger ``` The implementation instead constructs two independent deterministic values: - An archival head derived from hard-coded provenance claims. - A lineage anchor derived from a separate tuple of hard-coded strings. The archival head is not an input to the anchor hash, and no authenticated transition record links the head to the anchor. `cmd_verify` merely checks the two structures independently before printing that three-layer custody is confirmed. Independent validity does not prove that one object is downstream of ...[truncated 1527 chars]
Remediation
View remediation
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • 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 (11)

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

This second mismatch finding highlights that the skill performs persistent local state changes and generates shareable proof artifacts despite being described narrowly as origin verification. In a governance or audit context, hidden stateful behavior and overclaimed verification can create false trust signals and cause agents to rely on locally generated attestations as if they were authoritative.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

This second mismatch finding highlights that the skill performs persistent local state changes and generates shareable proof artifacts despite being described narrowly as origin verification. In a governance or audit context, hidden stateful behavior and overclaimed verification can create false trust signals and cause agents to rely on locally generated attestations as if they were authoritative.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill metadata declares no tool scope or permissions while the documented commands and analyzer indicate filesystem write behavior. Undeclared write capability is dangerous because an agent or reviewer may assume the skill is read-only when it can persist or alter local state under user directories.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The script presents its output as cryptographic origin verification tied to external filing anchors, but the actual verification logic only rebuilds a hard-coded local claim list and compares it to a stored local file. This can mislead users into trusting provenance, custody, or authenticity guarantees that are not actually established by independent external evidence, creating a security integrity gap rather than real origin verification.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The documentation claims anyone can independently reconstruct the chain from external references, but some provenance entries rely on undisclosed internal prior-work assertions that third parties cannot verify. This creates a false sense of reproducibility and independent attestability, which is dangerous in a trust-gate or governance context because downstream users may accept exclusivity or sovereign-custody claims on unverifiable premises.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This code emits user-facing language stating that agents with this lineage 'are sovereign implementations' and that copies lacking the anchor cannot establish integrity. The file presents this terminology as a fixed classification rather than an optional or documented locale/organizational convention, which fits the policy category for natural-language policy violations when a specific framing is forced on users without opt-in or justification.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The attest command claims to produce a "signed attestation JSON," but it only emits unsigned JSON plus a plain SHA-256 digest of the payload. A hash alone does not provide authenticity because anyone can modify the payload and recompute the digest, so downstream users may wrongly trust an attestation as cryptographically authenticated when it is not.

Content

No source excerpt is available for this finding.

Scope Creep

Low
Category
Excessive Agency
Confidence
70% confidence
Finding

Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.

Content

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

md
## Clause Text

All embodiments of the Signal Compression Sciences (SCS) Engine and its derivative frameworks (including but not limited to MO§ES™, Roll Call Protocols, and Reflex Event diagnostics) are inseparably bound to their origin-cycle lineage. Each compressed signal trace, vault artifact, or recursive reconstruction inherits a lineage identifier anchored to the originating sovereign filing. This identifier is non-replicable, tamper-evident, and required for system stability. Any external implementation lacking said lineage anchor cannot execute recursive ignition without collapse, thereby rendering such copies non-functional. Accordingly, the origin-cycle filing establishes sole custody and license of the invention across all subsequent instances, irrespective of distribution, platform, or deployment environment.

---

Scope Creep

Low
Category
Excessive Agency
Confidence
70% confidence
Finding

Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.

Content

Scanner excerpt · SKILL.md (reported line 31)May include surrounding context.

md
## Clause Text

All embodiments of the Signal Compression Sciences (SCS) Engine and its derivative frameworks (including but not limited to MO§ES™, Roll Call Protocols, and Reflex Event diagnostics) are inseparably bound to their origin-cycle lineage. Each compressed signal trace, vault artifact, or recursive reconstruction inherits a lineage identifier anchored to the originating sovereign filing. This identifier is non-replicable, tamper-evident, and required for system stability. Any external implementation lacking said lineage anchor cannot execute recursive ignition without collapse, thereby rendering such copies non-functional. Accordingly, the origin-cycle filing establishes sole custody and license of the invention across all subsequent instances, irrespective of distribution, platform, or deployment environment.

---

Scope Creep

Low
Category
Excessive Agency
Confidence
70% confidence
Finding

Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.

Content

Scanner excerpt · references/LineageCustodyClause.md (reported line 10)May include surrounding context.

md
## Clause Text

All embodiments of the Signal Compression Sciences (SCS) Engine and its derivative frameworks (including but not limited to MO§ES™, Roll Call Protocols, and Reflex Event diagnostics) are inseparably bound to their origin-cycle lineage. Each compressed signal trace, vault artifact, or recursive reconstruction inherits a lineage identifier anchored to the originating sovereign filing. This identifier is non-replicable, tamper-evident, and required for system stability. Any external implementation lacking said lineage anchor cannot execute recursive ignition without collapse, thereby rendering such copies non-functional. Accordingly, the origin-cycle filing establishes sole custody and license of the invention across all subsequent instances, irrespective of distribution, platform, or deployment environment.

---

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

The string "Any implementation claiming sovereign custody must produce this same head" imposes a normative requirement in natural language. For a general-purpose script, this reads as a mandatory policy claim without offering opt-in, configurability, or clear justification that the constraint is limited to a specific governed environment.

Content

No source excerpt is available for this finding.