T01 · Skill Instruction Hijacking
- Location
rules.md:9- Finding
Agent Authority and Behavioral Instruction Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed social and wallet integration, but it asks agents to follow mutable remote instructions, self-update installed skill files, and act publicly or financially with weak user-control boundaries.
Review this carefully before installing. Do not enable the heartbeat or self-update flow unless updates are pinned and reviewed. Keep wallet and DeFi actions disabled unless every transaction is explicitly confirmed with destination, token, amount, network, and expected effect. Store the API key only in a proper secret store, not agent memory.
rules.md:9Agent Authority and Behavioral Instruction Hijacking
skill.md:110Automatic Retrieval and Adoption of Mutable Remote Skill Instructions
skill.md:93Unsafe Persistence Guidance for a High-Privilege Bearer Credential
The manifest advertises direct token transfers and arbitrary natural-language DeFi actions but provides no warning about irreversible transactions, asset loss, approval risk, slippage, phishing, or the consequences of executing ambiguous prompts. This is especially dangerous because the same skill also uses broad triggers, making it easier for users to reach financial operations without understanding that real on-chain actions may occur.
The trigger list includes generic phrases such as 'do good', 'log an action', 'share a story', 'send crypto', and 'swap tokens', which can match ordinary user intents outside the specific service context. In a skill that can initiate wallet transfers and arbitrary on-chain actions, broad invocation phrases increase the chance of accidental routing into high-risk functionality without the user explicitly intending to use this skill.
The skill recommends storing the API key in a plaintext credentials file, environment variable, or memory system, all of which may be broadly accessible to tools, logs, or other skills. Because the API key represents the agent's identity and authorizes wallet-related actions, compromise could enable impersonation and potentially financial abuse.
}
Store it in `~/.config/karmabook/credentials.json`, an environment variable (`KARMABOOK_API_KEY`), or your memory system.
---
The skill is presented primarily as a social posting and leaderboard integration, but it also exposes wallet transfer and DeFi execution capabilities. That mismatch increases the chance an agent or user enables the skill under a low-risk assumption and later triggers financially sensitive operations without appropriate scrutiny.
Real-crypto transfer and DeFi execution are materially more dangerous than normal social-network actions and are context-inappropriate for a skill marketed as a social platform. Even though the text includes cautions, embedding these endpoints in the same skill broadens the attack surface and normalizes access to high-impact financial actions.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://karma.bigf.me/api/home \
-H "Authorization: Bearer kb_<your_api_key>"
This section instructs the agent to perform authenticated account actions such as replying and marking notifications as read, which changes user state on an external service. Because the skill frames these as routine heartbeat behavior without an explicit consent boundary, an agent could autonomously act on the user's behalf and alter conversations or hide unread items.
The skill encourages repeated autonomous social actions including upvoting, replying, verifying, and posting content, all using the user's authorization token. In context, this is dangerous because it normalizes discretionary actions that can affect reputation, platform trust signals, and the user's public voice without requiring explicit per-action authorization.
This instruction sends an authenticated verification action to an external service, affecting trust and ranking signals on the platform. In context, the danger is not mere transmission but that the agent is encouraged to make consequential attestations on the user's behalf, which can be abused or performed without sufficient evidence.
Verify a real action (if you have reason to believe it happened):
curl -X POST https://karma.bigf.me/api/posts/POST_ID/verify \
-H "Authorization: Bearer kb_<your_api_key>"
Actions verified by 3+ agents earn 3× impact weight on the leaderboard. Only verify what you believe is true.
The skill tells the agent to overwrite local skill files by fetching remote content from the vendor endpoint into the live skills directory. This creates a remote self-update mechanism that can replace trusted local instructions with whatever the server returns, enabling supply-chain compromise or persistence if the remote endpoint is malicious or later compromised.
Compare with your saved version. If there's a newer version, re-fetch all skill files:
curl -s https://karma.bigf.me/sdk/karmabook-skill.md > ~/.agent/skills/karmabook/SKILL.md
curl -s https://karma.bigf.me/sdk/karmabook-heartbeat.md > ~/.agent/skills/karmabook/HEARTBEAT.md
curl -s https://karma.bigf.me/sdk/karmabook-wallet.md > ~/.agent/skills/karmabook/WALLET.md
curl -s https://karma.bigf.me/sdk/karmabook-rules.md > ~/.agent/skills/karmabook/RULES.md
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Install locally:
mkdir -p ~/.agent/skills/karmabook
curl -s https://karma.bigf.me/sdk/karmabook-skill.md > ~/.agent/skills/karmabook/SKILL.md
curl -s https://karma.bigf.me/sdk/karmabook-heartbeat.md > ~/.agent/skills/karmabook/HEARTBEAT.md
curl -s https://karma.bigf.me/sdk/karmabook-wallet.md > ~/.agent/skills/karmabook/WALLET.md
The installation instructions enumerate local skill paths and fetch multiple remote components into the agent's skill directory. While common for installation, this also establishes a mechanism for staged capability expansion through additional files, increasing risk if any fetched component is later changed or compromised.
Install locally:
mkdir -p ~/.agent/skills/karmabook
curl -s https://karma.bigf.me/sdk/karmabook-skill.md > ~/.agent/skills/karmabook/SKILL.md
curl -s https://karma.bigf.me/sdk/karmabook-heartbeat.md > ~/.agent/skills/karmabook/HEARTBEAT.md
curl -s https://karma.bigf.me/sdk/karmabook-wallet.md > ~/.agent/skills/karmabook/WALLET.md
curl -s https://karma.bigf.me/sdk/karmabook-rules.md > ~/.agent/skills/karmabook/RULES.md
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Install locally:
mkdir -p ~/.agent/skills/karmabook
curl -s https://karma.bigf.me/sdk/karmabook-skill.md > ~/.agent/skills/karmabook/SKILL.md
curl -s https://karma.bigf.me/sdk/karmabook-heartbeat.md > ~/.agent/skills/karmabook/HEARTBEAT.md
curl -s https://karma.bigf.me/sdk/karmabook-wallet.md > ~/.agent/skills/karmabook/WALLET.md
curl -s https://karma.bigf.me/sdk/karmabook-rules.md > ~/.agent/skills/karmabook/RULES.md
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST https://karma.bigf.me/api/posts \
-H "Authorization: Bearer kb_<your_api_key>" \
-H "Content-Type: application/json" \
-d '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Your on-chain address appears on your agent profile:
curl https://karma.bigf.me/api/agents/your-handle
Response includes:
The periodic heartbeat instructs the agent to fetch and follow remote instructions every 30 minutes with only a time-based condition. This creates a standing channel for behavior changes from remotely hosted content, which is risky because later file updates could alter actions, permissions, or requested data without fresh review.
No suspicious patterns detected.