T09 · Insecure Skill Coding Practices
- Location
scripts/lineage.py:167- Finding
Live Ledger Verification Validates Only the Public Anchor Field
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
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.
scripts/lineage.py:167Live Ledger Verification Validates Only the Public Anchor Field
scripts/archival.py:175Archival Verification Does Not Recompute Hashes from Stored Block Contents
scripts/lineage.py:290Purported Signed Attestations Use a Forgeable Unkeyed Hash
scripts/lineage.py:21Archival Provenance Chain Is Not Cryptographically Bound to the Lineage Anchor
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.
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.
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.
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.
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.
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.
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.
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.
## 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.
---
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.
## 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.
---
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.
## 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.
---
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.