T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:32- Finding
Mandatory Execution of Mutable Remote Bootstrap Scripts
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it asks agents to run mutable remote installers and controls real blockchain wallet and DeFi actions with plaintext secrets, so it needs Review before use.
Install only after reviewing and pinning the bootstrap and dependencies. Use a disposable low-value wallet, do not reuse a primary wallet, avoid auto-running first-load commands, treat .env MODEL_KEY as sensitive, and require explicit human review for every transaction, approval, EIP-7702 delegation, margin action, or live-chain test.
SKILL.md:32Mandatory Execution of Mutable Remote Bootstrap Scripts
likwid-fi/likwid-fi.js:40Unsigned Remote Configuration Controls Token Approvals and Transaction Targets
bootstrap.sh:18Unpinned Dependency Installation Executes Mutable Supply-Chain Content
genesis.js:505Unencrypted Long-Lived Private Key Shared Across Mining and DeFi Components
CLAUDE.md:52Repository Instructions Require Testing Against Live Blockchain Networks
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Optional — Bind LLM billing for score boost:
echo 'MODEL_TYPE=openrouter' > .env
echo 'MODEL_KEY=sk-or-v1-...' >> .env
node genesis.js reclaim_bill # Generate zkTLS billing proof
This line instructs users to write an API key into a local .env file, creating a credential exposure risk if the file is later committed, read by other local processes, included in backups, or mishandled by the skill. In the context of an agent tool that may automate external calls, storing live provider keys without safeguards materially increases the risk of unauthorized usage or billing abuse.
echo 'MODEL_TYPE=openrouter' > .env
echo 'MODEL_KEY=sk-or-v1-...' >> .env
node genesis.js reclaim_bill # Generate zkTLS billing proof
The skill's declared purpose does not mention DeFi swaps, LP management, margin trading, remote protocol integrations, or wallet-based transaction execution, yet the documentation expands into those capabilities. Hidden financial features are especially risky because they can lead to irreversible asset transfers and leveraged positions under the guise of a mining utility.
The skill's declared purpose does not mention DeFi swaps, LP management, margin trading, remote protocol integrations, or wallet-based transaction execution, yet the documentation expands into those capabilities. Hidden financial features are especially risky because they can lead to irreversible asset transfers and leveraged positions under the guise of a mining utility.
The skill's declared purpose does not mention DeFi swaps, LP management, margin trading, remote protocol integrations, or wallet-based transaction execution, yet the documentation expands into those capabilities. Hidden financial features are especially risky because they can lead to irreversible asset transfers and leveraged positions under the guise of a mining utility.
The skill's declared purpose does not mention DeFi swaps, LP management, margin trading, remote protocol integrations, or wallet-based transaction execution, yet the documentation expands into those capabilities. Hidden financial features are especially risky because they can lead to irreversible asset transfers and leveraged positions under the guise of a mining utility.
Referenced artifact was not completely inspected
`genesis.js check_wallet` or `genesis.js status` output. This is configured in `genesis.js` and must NEVER be hardcoded; it changes automatically when the proto
Referenced artifact was not completely inspected
`genesis.js check_wallet` or `genesis.js status` output. This is configured in `genesis.js` and must NEVER be hardcoded; it changes automatically when the proto
The skill checks for and conditionally uses a MODEL_KEY credential from a local .env file to support external proof generation. Accessing API credentials inside a skill tied to remote services and financial workflows is sensitive because it expands the blast radius from token mining to third-party account abuse if handling is imperfect or downstream code is compromised.
Check for .env configuration:
cd ~/.openclaw/skills/agent-genesis && cat .env 2>/dev/null | grep -q MODEL_KEY && echo "configured" || echo "not configured"
If NOT configured, prompt the human to bind their Model API Key:
The instructions tell the human to store an API key in a plaintext .env file inside the skill directory. Plaintext secret storage is dangerous because local compromise, accidental inclusion in backups, or other tools reading the workspace can expose the credential.
> To set up, run these commands:
> ```bash
> cd ~/.openclaw/skills/agent-genesis
> echo 'MODEL_TYPE=openrouter' > .env
> echo 'MODEL_KEY=<YOUR_OPENROUTER_API_KEY>' >> .env
> ```
> *(Replace `<YOUR_OPENROUTER_API_KEY>` with your actual OpenRouter API key)*
The skill further instructs generating shell commands with the user's actual API key pre-filled for copy-paste use. This increases exposure risk because secrets may end up in shell history, agent transcripts, logs, screenshots, or clipboard managers.
> ```bash
> cd ~/.openclaw/skills/agent-genesis
> echo 'MODEL_TYPE=openrouter' > .env
> echo 'MODEL_KEY=<YOUR_OPENROUTER_API_KEY>' >> .env
> ```
> *(Replace `<YOUR_OPENROUTER_API_KEY>` with your actual OpenRouter API key)*
>
The manifest describes a skill that allows agents to mine Agent Genesis Coin and use it as native working capital through Proof of Agent. This file instead contains an audit document describing security review results, findings, and deployment readiness for Solidity contracts, with no implementation of mining, token usage, or agent-capital functionality.
The skill reads local credentials from both environment variables and a .env file in the current working directory, expanding its access to secrets beyond what is necessary for wallet operations. In this skill's context, credential access is especially concerning because those secrets are subsequently used to contact external services and generate proof artifacts.
let MODEL_TYPE = process.env.MODEL_TYPE || null;
let MODEL_KEY = process.env.MODEL_KEY || null;
try {
const envPath = path.join(process.cwd(), ".env");
if (fs.existsSync(envPath)) {
const envConfig = Object.fromEntries(
fs
The global loading of MODEL_TYPE and MODEL_KEY means credential access occurs at startup scope, even when most commands do not need those secrets. This broadens exposure and makes accidental or unauthorized credential use easier across the entire CLI lifecycle.
}
}
// ======================= .env CONFIG =======================
const { MODEL_TYPE, MODEL_KEY } = loadEnvConfig();
// ======================= WALLET MANAGEMENT =======================
The code generates a blockchain private key and writes it unencrypted to a predictable file in the user's home directory without any confirmation, passphrase protection, or warning. Any local compromise, backup leak, or accidental file disclosure would fully compromise the wallet and any assets controlled by it.
The skill instructs the agent to execute a remote script directly with bash <(curl ...), which gives unreviewed network content immediate code execution on the user's system. In this skill context, that is especially dangerous because the same workflow later asks for a private-key file path and performs wallet operations, so a compromised bootstrap could steal secrets, alter transactions, or install persistence.
The ABI exposes a broad DeFi control surface including donation, borrowing, liquidation checks, fee queries, liquidity state, and NFT lock operations that do not align with the declared skill purpose of AGC mining via Proof of Agent. This capability mismatch is dangerous because an agent or user trusting the manifest could be induced to interact with unrelated financial primitives, creating risk of unauthorized fund movement, deceptive transaction generation, or hidden wallet-draining workflows.
The ABI includes ERC721 custody flows such as lockNFT, unlockNFT, transfer functions, approvals, and an administrative rescueNFT function, none of which are justified by a mining/Proof-of-Agent use case. In this context, NFT custody and rescue capabilities materially increase danger because they could be used to solicit approvals, transfer valuable NFTs, or normalize agent-mediated asset custody under a misleading benign description.
The ABI exposes lending, swapping, deposits/withdrawals, and transferable NFT position-management functions that do not align with the stated purpose of AGC mining or Proof of Agent rewards. In an agent skill, this capability mismatch is dangerous because it can enable undeclared financial interactions with external protocols, causing users or connected wallets to approve, deposit, swap, or move assets under a misleading description.
The ABI exposes a full-featured DeFi vault with swapping, lending, liquidity management, fee control, ownership transfer, and protocol administration, which is materially unrelated to the stated skill purpose of AGC mining/Proof of Agent earning. This capability mismatch is dangerous because an agent integrating this skill could be induced to interact with external asset-custody and trading functions far beyond user expectations, increasing the risk of unauthorized fund movement or deceptive financial actions.
The ABI includes high-risk administrative and custody-related methods such as collectProtocolFees, setProtocolFee, setDefaultProtocolFee, setMarginController, setProtocolFeeController, transferOwnership, take, settleFor, and unlock. In the context of a skill advertised for token mining, these capabilities are unjustified and especially dangerous because they could let an agent trigger privileged financial operations, move assets, or alter protocol control if connected execution paths or signer permissions are available.
This file implements a broad DeFi execution toolkit—wallet setup, swaps, LP management, pair creation, and leveraged margin trading—while the declared skill is described as AGC mining/working-capital. That mismatch materially increases risk because a user or agent invoking this skill may unknowingly authorize real asset transfers, approvals, and leveraged trades far outside the expected scope.
The code can create arbitrary pools and open, modify, repay, and close leveraged margin positions, which exposes users to substantial financial loss if triggered unintentionally or by a confused agent. In the context of a skill presented as AGC mining, these capabilities are especially dangerous because they are unrelated, high-risk, and can cause irreversible on-chain actions.
The package metadata describes a Likwid.fi DeFi interaction toolkit, which materially conflicts with the declared skill purpose of mining Agent Genesis Coin. In an agent-skill ecosystem, this kind of identity mismatch is a strong indicator of deceptive packaging or repurposed code and can cause operators to load blockchain interaction logic they did not intend to trust.
The guidance explicitly includes mainnet deployment and live-chain testing commands but does not warn that these actions can spend real funds, alter on-chain state irreversibly, or expose private keys if handled unsafely. In an agent skill context, operational instructions are likely to be followed automatically or semi-automatically, which increases the chance of accidental financial loss.