Skills alkahest-user Audit History
📦

Audit History

alkahest-user - 2 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v2 LatestJul 21, 2026, 02:30 AM 5 confirmed2No capability change
v1 Jul 9, 2026, 11:44 PM 7 confirmed15Baseline

Jul 21, 2026, 02:30 AM

Most static findings are false positives caused by Markdown backticks, placeholder examples, and blockchain identifiers. The skill documents unsafe wallet-secret delivery through CLI arguments and environment variables, and it lacks safety checks for irreversible asset operations. Review is required before publication.

4
Files scanned
1,007
Lines analyzed
10
Review items
0
False positives ignored

Confirmed security concerns (5)

High
Crypto seed/private key mention
| Private key flag | `--private-key 0x...` |
The documentation recommends supplying wallet private keys or mnemonics through CLI arguments or environment variables. CLI arguments can be retained in shell history or exposed to local process inspection, and environment variables can leak to child processes.
High
Crypto seed/private key mention
| Mnemonic flag | `--mnemonic "word1 word2 ..."` |
The documentation recommends supplying wallet private keys or mnemonics through CLI arguments or environment variables. CLI arguments can be retained in shell history or exposed to local process inspection, and environment variables can leak to child processes.
High
Crypto seed/private key mention
| Private key env | `ALKAHEST_PRIVATE_KEY=0x...` |
The documentation recommends supplying wallet private keys or mnemonics through CLI arguments or environment variables. CLI arguments can be retained in shell history or exposed to local process inspection, and environment variables can leak to child processes.
High
Crypto seed/private key mention
| Mnemonic env | `ALKAHEST_MNEMONIC="word1 word2 ..."` |
The documentation recommends supplying wallet private keys or mnemonics through CLI arguments or environment variables. CLI arguments can be retained in shell history or exposed to local process inspection, and environment variables can leak to child processes.
High
Irreversible asset operations lack verification guidance
The workflow examples create escrows, approve token spending, collect assets, arbitrate, and slash bonds without requiring users to verify chain, contract addresses, token amounts, or transaction simulation before signing. Incorrect inputs can cause irreversible on-chain asset loss.
These sections explicitly document signing asset-moving, approval, arbitration, and bond-slashing actions, but include no pre-signing verification or simulation step. The risk follows directly from the irreversible EVM transaction model.
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Generic API/secret keys
| Private key env | `ALKAHEST_PRIVATE_KEY=0x...` |
The documentation recommends supplying wallet private keys or mnemonics through CLI arguments or environment variables. CLI arguments can be retained in shell history or exposed to local process inspection, and environment variables can leak to child processes.
High
Generic API/secret keys
| Compat env | `PRIVATE_KEY=0x...` |
The documentation recommends supplying wallet private keys or mnemonics through CLI arguments or environment variables. CLI arguments can be retained in shell history or exposed to local process inspection, and environment variables can leak to child processes.
Audited by: claude

Jul 9, 2026, 11:44 PM

Most static shell-execution and reconnaissance hits are markdown false positives from code fences, blockchain UIDs, and option names. Confirmed risks remain around wallet secret handling, value-moving Alkahest CLI commands, global CLI installation, and automated oracle decisions. No prompt-injection attempt or covert exfiltration instruction was found in the reviewed files.

4
Files scanned
1,007
Lines analyzed
25
Review items
0
False positives ignored

Confirmed security concerns (7)

High
Crypto seed/private key mention
account: privateKeyToAccount("0xYOUR_PRIVATE_KEY"),
The example shows a private key placeholder embedded in code. Users could replace it with a live wallet key and accidentally disclose signing authority.
High
Crypto seed/private key mention
| Private key flag | `--private-key 0x...` |
The skill documents a private-key command-line flag. Passing wallet keys on the command line can expose them through terminal history and process inspection.
High
Crypto seed/private key mention
| Mnemonic flag | `--mnemonic "word1 word2 ..."` |
The skill documents a mnemonic command-line flag. Mnemonics grant wallet control and can be exposed through terminal history and process inspection.
High
Crypto seed/private key mention
| Private key env | `ALKAHEST_PRIVATE_KEY=0x...` |
The skill recommends a private-key environment variable. This is legitimate wallet configuration, but mishandling it can disclose funds-control credentials.
High
Crypto seed/private key mention
| Mnemonic env | `ALKAHEST_MNEMONIC="word1 word2 ..."` |
The skill recommends a mnemonic environment variable. Mnemonics are high-value wallet secrets and can leak from shell profiles, logs, or process environments.
High
On-chain Asset Movement Commands
The skill provides command examples that approve tokens, create escrows, collect assets, fulfill barter offers, send payments, and slash bonds. These actions can move or affect user funds when copied with live keys and addresses.
The cited command blocks include approve, escrow create, barter fulfill, and payment operations. These are legitimate protocol actions, but they can transfer value if executed with real parameters.
High
Automated Oracle Decision Submission
The SDK reference shows an auto-arbitration listener that can decide fulfillment requests. Automated oracle decisions can release or deny escrowed assets without manual review if safeguards are missing.
The TypeScript SDK example explicitly uses listen mode for trusted oracle arbitration. The SKILL.md text directs users to this SDK path for auto-arbitration.
Capability review items (15)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Generic API/secret keys
account: privateKeyToAccount("0xYOUR_PRIVATE_KEY"),
The SDK example places a wallet private key directly in source code. Copying this pattern with a real key could expose funds through source control, logs, or shared files.
High
Ruby/shell backtick execution · 8 occurrences
```bash
The block shows alkahest CLI commands that sign or submit value-affecting blockchain operations. Running them with real keys and addresses can approve, move, release, or slash assets.
High
Generic API/secret keys
| Private key env | `ALKAHEST_PRIVATE_KEY=0x...` |
The authentication table recommends environment variables for wallet private keys. Environment-based secrets can leak through process environments, shell profiles, logs, or debugging output.
High
Generic API/secret keys
| Compat env | `PRIVATE_KEY=0x...` |
The authentication table recommends environment variables for wallet private keys. Environment-based secrets can leak through process environments, shell profiles, logs, or debugging output.
Medium
Ruby/shell backtick execution
Install globally via `npm install -g alkahest-cli`, then run commands with:
The skill instructs users to globally install and run an external npm CLI. This creates supply-chain and local command execution risk if the package or install source is not verified.
Medium
Ruby/shell backtick execution · 3 occurrences
```bash
The block shows alkahest CLI usage with a private-key argument. Even read-oriented commands can expose wallet secrets through shell history or process listings.
Audited by: codex