📦

Audit History

alkahest-developer - 2 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v2 LatestJul 21, 2026, 02:28 AM No confirmed findings0No capability change
v1 Jul 9, 2026, 11:39 PM 2 confirmed11Baseline

Jul 21, 2026, 02:28 AM

All 118 static detections are false positives caused by Markdown formatting, SDK examples, placeholder RPC URLs, and placeholder private keys. The reviewed files contain no executable shell commands, credential exfiltration, or prompt-injection instructions. The skill documents blockchain operations, so users must independently validate transaction details before signing.

5
Files scanned
1,327
Lines analyzed
4
Review items
0
False positives ignored

Risk Factors

⚡ Contains scripts (4)
🌐 Network access (13)
🔑 Env variables (12)
⚙️ External commands (50)
Audited by: claude

Jul 9, 2026, 11:39 PM

Most static findings are markdown or SDK reference false positives, including code fences, TypeScript template literal types, and blockchain UID fields. The audit confirms repeated inline private-key placeholders in setup examples as a real copy-paste safety risk for wallet code. No prompt injection, data-exfiltration intent, or unauthorized command execution evidence was found.

5
Files scanned
1,327
Lines analyzed
17
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Crypto seed/private key mention
account: privateKeyToAccount("0xKEY"),
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.
High
Crypto seed/private key mention
account: privateKeyToAccount("0xPRIVATE_KEY"),
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.
Capability review items (11)

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 · 2 occurrences
client = PyAlkahestClient("0xPRIVATE_KEY", "https://rpc-url")
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.
High
Generic API/secret keys · 2 occurrences
client = PyAlkahestClient("0xPRIVATE_KEY", "https://rpc-url", config)
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.
High
Generic API/secret keys · 4 occurrences
"0xPRIVATE_KEY",
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.
High
Generic API/secret keys · 2 occurrences
let bare = AlkahestClient::new("0xPRIVATE_KEY", "https://rpc-url").await?;
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.
High
Generic API/secret keys
account: privateKeyToAccount("0xPRIVATE_KEY"),
The example passes private-key material as an inline string during wallet or client setup. The value is a placeholder, not a leaked key, but the copy-paste pattern is unsafe for blockchain wallet code.

Risk Factors

⚡ Contains scripts (4)
🌐 Network access (13)
🔑 Env variables (12)
⚙️ External commands (50)
Audited by: codex