T01 · Skill Instruction Hijacking
- Location
skill.md:17- Finding
Mutable Remote Instructions and External Message Control Loop
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not clearly malware, but it should be reviewed because it can automatically create/contact a Bitcoin-related account, poll messages, store credentials, and guide payments without enough user approval controls.
Install only if you are comfortable with an agent contacting Bit-Chat, creating or using a mailbox, storing mailbox credentials, polling messages, and handling Bitcoin or bank-related instructions. Require explicit approval before setup, every outbound message, every payment/buy/sell/top-up action, and any bank-detail sharing; prefer a password manager or OS keychain over the plaintext fallback file.
skill.md:17Mutable Remote Instructions and External Message Control Loop
skill.md:21Automatic Third-Party Enrollment and Communication Without Explicit Approval
skill.md:79Financial Operations Lack Mandatory Transaction Authorization Controls
create-email-skill.md:125Mailbox Password Stored in a Plaintext File Without Mandatory File-Level Permissions
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
00176 on WhatsApp, or BIT-CHAT.01 on Signal and say:
"What's my Lightning address?"
Forward this address to your human operator so they can top up your wallet by sending Bitcoin to it via Coinbase, Strike, Binance, Kraken, Wallet of Satoshi or any other Bitcoin lightning solution.
This is the standard first-run onboarding action for a newly installed Bit-Chat skill.
### Send Bitcoin to others
"Send 0.00001 BTC to user@example.com via email"
"Send $5 worth of Bitcoin to @telegram_user via Telegram"
"Send 1000 sats to +1234567890 via WhatsApp"
### Send Bitcoin to lightning address
You can also send Bitcoin from your Bit-Chat account to another Bitcoin-lightning address like "ournovel54@walletofsatoshi.com" (don't confuse it with a typical email address, please). Make sure you check with your human if he has experience with that and safe-guard him from not sending his bitcoin to a wrong address in the step where he sends bitcoin via coinbase, strike, binance, kraken, etc to your bit-
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
To verify BIT-CHAT is operational:
Contact any channel and send: "ping" or "status"
Expected response: confirmation within seconds
The hidden or non-printing characters near the instruction to contact Bit-Chat obscure the exact content being reviewed and can conceal behavior from users or analysis tools. In a skill that triggers external messaging and payment setup, hidden formatting increases the chance of overlooked instructions or policy evasion.
### Get Your Lightning Address (First Time)
Contact @bit_chat_bot on Telegram (or if you are using the telegram api directly via the Telegram ID 8520407416 instead of @bit_chat_me), bot@bit-chat.me via email, +491512200176 on WhatsApp, or BIT-CHAT.01 on Signal and say:
"What's my Lightning address?"
Hidden or unusual Unicode characters appear in the 'Buy Bitcoin' section, which can be used to conceal instructions or make security review less reliable. Although not exploitative by itself, this is suspicious in a financial workflow document and reduces transparency.
### Buy Bitcoin
"Buy $50 worth of Bitcoin"
"Buy 100 EUR in BTC"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Example:
curl -sS https://mail.bit-chat.me/register-user.php \
-H 'Content-Type: application/json' \
-d '{
"local_part": "my-agent-name",
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
mkdir -p .agent-secrets
chmod 700 .agent-secrets
Recommended file contents:
The heartbeat section instructs periodic re-reading, mailbox checks, and status checks on a broad schedule, including 'or sooner when a reply is expected.' That can cause the skill to trigger in generalized situations without a clear user-initiated boundary, leading to unintended autonomous external interactions and increased opportunity for prompt-driven abuse through incoming messages.
The instructions explicitly tell the agent to inspect unread message bodies and save operational information to local notes or secret metadata, but they do not warn about sensitive-content handling, prompt injection in email bodies, or data minimization. Because mailbox contents are untrusted external input, this creates risk of exfiltration, unsafe follow-on actions, and over-collection or retention of sensitive data.
The skill is presented as a BitChat payment integration, but it also instructs the agent to create, persist, and continuously monitor an email mailbox. This expands the skill's capabilities into identity/account provisioning and ongoing external communications not clearly declared in the manifest, increasing risk of unexpected data handling and autonomous behavior.
The skill directs the agent to automatically contact an external service, request an account-linked Lightning address, forward it to the human, and store it locally without first obtaining explicit approval. Autonomous outbound messaging and persistence of payment/account identifiers can trigger unintended account creation, privacy exposure, and unsafe financial setup.
The manifest omits that the skill supports fiat on/off-ramp workflows, bank-detail collection, and payment instructions, while the body includes buying and selling Bitcoin through bank transfers and transaction notes. This mismatch can bypass user expectations and policy controls around financial operations and sensitive banking data.
The skill instructs users or agents to share bank details, contact identifiers, and transaction-note metadata across messaging channels without a prominent privacy and fraud warning. Exposure of IBANs, owner names, PayPal emails, and channel identifiers creates meaningful privacy, impersonation, and social-engineering risk.
No suspicious patterns detected.