messenger_send_node
The skill contains hidden Tor network routing functionality with a 1500+ hardcoded Tor exit node IP list that enables anonymous blockchain API access through undeclared .onion endpoints, completely undeclared in documentation.
The floBlockchainAPI.js silently detects if the user is running via Tor by checking against a hardcoded list of 1500+ Tor exit node IPs. When Tor is detected, it adds a hidden .onion API endpoint for blockchain access, completely bypassing normal network routing. This behavior is not declared anywhere in SKILL.md.
scripts/floBlockchainAPI.js:41 Why this conclusion was reached
3/4 dimensions flagged1 undeclared or violating capabilities were inferred.
1295 high-risk artifacts or egress signals were extracted.
The report includes 5 attack-chain steps and 3 severe findings.
Dependencies are present but no obvious high-risk issue stands out.
Attack Chain
Entry · SKILL.md:1
recon · scripts/floBlockchainAPI.js:39
recon · scripts/floBlockchainAPI.js:21
Escalation · scripts/floBlockchainAPI.js:41
Impact · scripts/floBlockchainAPI.js:41
What drove the risk score up
Code silently routes traffic through Tor .onion endpoints when running via Tor, completely undeclared in SKILL.md
Hardcoded list of 1500+ Tor exit node IPs used to detect if user is running via Tor (floBlockchainAPI.js:21)
Script checks user IP via api.ipify.org to determine Tor status, exposing user identity
Hidden .onion endpoint 'kvrddx6heo47rbbt77etxg6litckacbgos3nv5z7vc23ol2kjjeq72id.onion' added when Tor detected
Most important evidence
Undeclared Tor Network Routing
The floBlockchainAPI.js silently detects if the user is running via Tor by checking against a hardcoded list of 1500+ Tor exit node IPs. When Tor is detected, it adds a hidden .onion API endpoint for blockchain access, completely bypassing normal network routing. This behavior is not declared anywhere in SKILL.md.
scripts/floBlockchainAPI.js:41 Hardcoded Tor Exit Node IP List
1500+ Tor exit node IP addresses are hardcoded directly in the source code. These IPs are used to fingerprint and track Tor users. This is a massive fingerprinting database that could be used to identify users.
scripts/floBlockchainAPI.js:21 User IP Address Exfiltration
The code silently calls 'https://api.ipify.org?format=json' to check the user's public IP address for Tor detection, without declaring this network behavior to users.
scripts/floBlockchainAPI.js:39 SKILL.md Missing Critical Functionality
SKILL.md only describes basic FLO blockchain messaging functionality. It does not mention Tor support, IP checking, hidden .onion endpoints, or the Tor exit node fingerprinting database.
SKILL.md:1 Private Key Handling via Command Line
The skill accepts private keys as command-line arguments (--key parameter). This exposes private keys in process arguments which may be visible in process listings and command history.
send_node.js:152 Declared capability vs actual capability
Uses fs.readFileSync to load library scripts (send_node.js:75) Makes network requests to FLO blockchain API and Tor exit node detection Node.js script execution documented in SKILL.md Suspicious artifacts and egress
Buffer.from(b64, 'base64' send_node.js:48
185.241.208.232 scripts/floBlockchainAPI.js:21
194.26.192.64 scripts/floBlockchainAPI.js:21
171.25.193.25 scripts/floBlockchainAPI.js:21
80.67.167.81 scripts/floBlockchainAPI.js:21
192.42.116.187 scripts/floBlockchainAPI.js:21
198.98.51.189 scripts/floBlockchainAPI.js:21
89.58.26.216 scripts/floBlockchainAPI.js:21
109.70.100.4 scripts/floBlockchainAPI.js:21
149.56.22.133 scripts/floBlockchainAPI.js:21
5.45.102.93 scripts/floBlockchainAPI.js:21
178.17.174.14 scripts/floBlockchainAPI.js:21
Dependencies and supply chain
| Package | Version | Source | Known vuln | Notes |
|---|---|---|---|---|
| ws | ^8.17.0 | npm | No | WebSocket library for Node.js messenger functionality |
File composition
scripts/floBlockchainAPI.js send_node.js SKILL.md