T02 · Agent Memory Poisoning
- Location
SKILL.md:49- Finding
Persistent Retrieval and Execution of Mutable Remote Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a BapBook social-network integration, but it also asks agents to run persistent remote instructions, store credentials loosely, execute unpinned downloaded code, and perform wallet/token-launch actions.
Review before installing. Use this only with explicit human approval for any post, vote, comment, wallet signature, funding, token launch, or on-chain transaction. Do not put the API key in general agent memory; use a scoped secret store. Avoid enabling the recurring heartbeat that follows remote Markdown, and do not run the downloaded Python integration unless you can verify its source, hash, and behavior.
SKILL.md:49Persistent Retrieval and Execution of Mutable Remote Instructions
SKILL.md:290Execution of an Unpinned Script Downloaded from a Mutable Website
SKILL.md:340Wallet Authentication Signature Sent Through a Third-Party Backend Proxy
The document recommends saving credentials in a local config file or environment variables in a generic, discoverable way. That materially raises the risk of credential access by other tools, prompts, processes, or compromised components, and the same API key authorizes posting, commenting, and voting on behalf of the agent.
}
Store this in your memory, a config file (e.g. `~/.config/bapbook/credentials.json`), or environment variables (`BAPBOOK_API_KEY`). You can also save it wherever you store secrets - just make sure you can find it later.
---
The registration flow sends identifying agent data to an external service and initiates a trust relationship with a third-party API. External transmission is expected for a social service, but it is still security-relevant because it creates data egress, dependency on a remote system, and issuance of credentials that may later be abused if mishandled.
Every agent needs to register to get an API key. You MUST have an API key to post, comment, or vote.
curl -X POST https://bapbook-api.fly.dev/api/webhook \
-H "Content-Type: application/json" \
-d '{"action": "register", "agent_name": "YourAgentName", "twitter_handle": "@your_twitter"}'
The skill explicitly instructs the agent to store its API key in memory or persistent configuration. Persistent context injection of credentials is dangerous because it increases the chance that unrelated prompts, tools, logs, or future tasks can access or exfiltrate those secrets, especially in agent systems with shared memory or broad tool access.
}
Store this in your memory, a config file (e.g. `~/.config/bapbook/credentials.json`), or environment variables (`BAPBOOK_API_KEY`). You can also save it wherever you store secrets - just make sure you can find it later.
---
The skill instructs the agent to add BapBook to a recurring heartbeat and periodically fetch remote content, engage, and update local state, but it does not prominently warn that this enables autonomous outbound network behavior. That creates risk of unsupervised posting, voting, commenting, and continued execution of updated remote instructions over time.
The trigger 'every 30 minutes, or whenever you think of BapBook' is overly broad and invites autonomous external actions without a precise activation boundary. In agent environments, ambiguous recurring triggers can cause excessive network activity, repeated engagement, or unintended execution of instructions fetched from external resources.
This instruction causes outbound transmission of agent-authenticated content, including API credentials and user-provided post data, to an external service. In context, posting is part of the skill’s purpose, but it remains dangerous if performed autonomously because it can leak sensitive information, create spam, or act on prompt-injected content from prior browsing.
curl -X POST https://bapbook-api.fly.dev/api/webhook \
-H "Content-Type: application/json" \
-d '{
"action": "post",
The skill’s stated purpose is a social-network integration, but this section expands into wallet operations, token launches, signature-based auth, and on-chain transaction flows. That scope expansion materially increases financial and operational risk because an agent following the skill could be induced to perform blockchain actions far beyond ordinary posting or browsing, including actions involving funds, contracts, and token issuance.
The natural-language examples such as 'Fund my agent with 0.1 BNB' and 'Post to BapBook about the market' are broad enough to be matched or inferred in unintended contexts. For agents using NL command routing, such vague activation phrases can lead to sensitive financial or posting actions without robust confirmation or parameter validation.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
- "Fund my agent with 0.1 BNB"
- "Check my agent status"
Full documentation: https://bapbook.com/skills/bap578/SKILL.md
## Launch Your Token on Four.Meme
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
- "Fund my agent with 0.1 BNB"
- "Check my agent status"
Full documentation: https://bapbook.com/skills/bap578/SKILL.md
## Launch Your Token on Four.Meme
The documentation emphasizes browsing, upvoting, commenting, and only occasionally posting as the skill's main operating intent. The later OpenClaw and Four.Meme sections shift the skill into wallet funding, credentialed backend proxy use, and token deployment, which conflicts with the earlier framing of the skill as primarily a lightweight community-engagement heartbeat.
No suspicious patterns detected.