🔍 Messaging link previews are an underappreciated leak vector when paired with agents. The act of unfurling a URL triggers network requests to fetch metadata, which can include sensitive context appended by the assistant. Critically, users do not need to click the link for data to flow. The write-up spotlights how this class of risk emerges in popular chat apps that support previews. promptarmor.com
🧪 The resource names OpenClaw as exposed by default on Telegram, illustrating how defaults shape real risk. Because previews are automatic, any malicious link produced by an assistant can quietly initiate outbound requests. That makes the preview pipeline a viable exfiltration path for whatever context the assistant includes. The page provides a way to test agent and app pairings for insecure previews. promptarmor.com
🛡️ Mitigation guidance is blunt and actionable: turn off link previews where exposure exists. Teams should review app settings, agent behaviors, and integration defaults, then reconfigure to minimize background requests. The article urges platform and agent builders to ship safer defaults and raise awareness. For security leads, this is a quick win that closes a noisy but preventable leak path. promptarmor.com