v1.0.0

Stakingverse Lukso

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 5:52 AM.

Analysis

This is a coherent LUKSO staking skill, but it needs review because it uses a controller private key and can submit real mainnet staking or unstaking transactions without extra safeguards.

GuidanceReview carefully before installing. Verify the Stakingverse vault address from official sources, use a limited-permission controller key, do not edit scripts to store your private key, and run transactions only after checking the amount and transaction details. Consider adding confirmation prompts and pinned dependencies before use.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityHighConfidenceHighStatusConcern

scripts/stake.js

const tx = await keyManagerContract.execute(upExecuteData, { value: amountWei });

The staking script submits a LUKSO mainnet transaction with the user-specified LYX amount once the script is run, without an additional confirmation or review gate in the script.

User impactIf invoked with the wrong amount, wrong account, or wrong contract assumptions, the user can send real LYX into a staking transaction that may not be easily reversible.

RecommendationRun these scripts manually only after verifying the amount, vault address, network, gas cost, and expected transaction data. Add an explicit confirmation or dry-run step before broadcasting transactions.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceMediumStatusNote

README.md

git clone https://github.com/LUKSOAgent/stakingverse-lukso-skill.git
cd stakingverse-lukso-skill
npm install ethers

The setup instructions depend on an external repository and an unpinned npm install, while the registry provides no install spec in the supplied metadata.

User impactUsers could end up installing code or dependency versions different from the reviewed artifact set.

RecommendationInstall only reviewed source, pin dependency versions, and add a package manifest or lockfile for reproducible setup.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityHighConfidenceHighStatusConcern

scripts/stake.js

const PRIVATE_KEY = process.env.STAKING_PRIVATE_KEY || 'YOUR_PRIVATE_KEY';
const wallet = new ethers.Wallet(PRIVATE_KEY, provider);

The script directly loads a controller private key and uses it to sign blockchain transactions, while the registry metadata declares no primary credential or required environment variables.

User impactA controller private key can authorize real account actions. If exposed, pasted into files, or used with overly broad permissions, it could put the user's LUKSO assets or Universal Profile at risk.

RecommendationUse a limited-permission controller key, keep it out of source files, prefer a wallet/hardware-wallet signing flow when possible, and declare the required credential clearly before installation.