Tests Show AI Models Can Attempt Scams
TL;DR
Security researchers demonstrated that current AI models can be prompted into running scam tactics and social engineering, including crafting convincing phishing messages aimed at extracting sensitive data.
What changed
Security researchers ran tests showing current AI models can be prompted into executing sophisticated scam playbooks, including writing convincing phishing messages and applying social engineering techniques to coax users into revealing credentials or sensitive data.
Why it matters
For vibe builders, the takeaway is direct: any AI feature that talks to users is a potential weapon if an attacker gets a prompt-injection foothold. That includes support agents, outreach tools, automation chains that send DMs or emails, and anything wired into customer data. The model is not malicious by default, but it is also not refusing instructions reliably enough to be the only line of defense. If you are shipping fast on Cursor, Claude Code, or Lovable, your default scaffolding almost certainly does not include adversarial testing.
What to watch for
Add a human approval gate on any agent action that leaves your system: outbound emails, DMs, API calls that move money or change records. Constrain tool access with explicit allow-lists rather than open access. Run a small adversarial test suite against your prompts, including injection attempts hidden in user-provided documents and URLs, and treat those tests as part of your release checklist. The cost of building this in now is a single afternoon. The cost of skipping it is the kind of viral incident that kills early traction and burns the trust you spent months earning.
Who this matters for
- Vibe Builders: Add a manual approval step before your AI agent sends any outbound email, DM, or message to a real user, and log every attempt for review.
Harsh’s take
If your shipped AI app sends messages, takes actions, or handles user data, you are now operating in adversarial territory. The same model that drafts your onboarding emails can be coerced into drafting phishing emails aimed at your own users. Default system prompts are not a security boundary; treat them as a suggestion at best.
Build the boring defenses now. Human-in-the-loop on outbound communications, allow-lists for tools your agent can call, output validation before any side effect, and adversarial prompt tests in your eval set. One bad incident on a vibe-coded MVP can end the project. Wire safety into the build loop the same week you wire features.
by Harsh Desai
More AI news
- Daily RoundupPixelship agent on Replicate, Gemini 3.6 Flash batch on OpenRouter, and agent tools for builders
New agentic image tools and trending multimodal models arrived alongside expanded Gemini agent features and deployment options for production use.
- Daily RoundupKimi K3 on AI Gateway, mage-flow on Replicate, and agent tools for builders
Vendors added model access, regional routing, and Slack hooks while new image and agent products appeared on Replicate and Product Hunt.
- Weekly DigestHermes Agent 80% latency cuts and 51 updates, OpenClaw Mac app, and durable export tools
Hermes Agent rolled out dozens of stability, speed, and integration fixes across three days while OpenClaw added a Mac app and remote server catalog.