Urgent.News

What's breaking now, across thousands of outlets.

Tech

Microsoft says email spammers are adopting ASCII smuggling, an AI prompt injection tactic used to hide malicious instructions, to evade email platform filters (Dan Goodin/Ars Technica)

A clever technique used to hide malicious prompts in attacks on AI agents has been adopted by spammers to evade filters …

Microsoft has reported that spammers are using a technique called ASCII smuggling to evade email filters. This technique, typically used to hide malicious prompts in AI attacks, involves embedding invisible Unicode characters in emails to conceal malicious instructions. According to Microsoft researchers Noam Kochavi and Sarah Wolstencroft, cited by The Register, ASCII smuggling allows attackers to hide content inside text that appears normal to humans but can be decoded by computers.

The Register and Ars Technica reports that Microsoft uncovered a massive phishing campaign using this technique, which peaked at over 2.37 million messages in late February and remained elevated over the next three months. The campaign used invisible Unicode tag characters to hide malicious prompts, making it difficult for email filters to detect. As The Register notes, this technique is popular for indirect prompt injection attacks, where an attacker hides instructions for an AI assistant in invisible Unicode characters.

Ars Technica provides more details on ASCII smuggling, explaining that it uses a special range of Unicode tags that mimic the American Standard Code for Information Interchange. These tags, such as U+E0041 and U+E0061, encode characters that are readable by computers but almost completely invisible to humans. By expressing malicious prompts in these tags, attackers can hide instructions that are detectable by AI models but not by humans reading the email.

Brief written by urgent.news from Techmeme, The Register, The Register Science, Ars Technica — 4 reports on this story. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at arstechnica.com →

More in Tech

Who Can Still Push to main? An Access and Process Audit in 30 Seconds

The question is not who has push access to main — that is an access-control question, answered in the platform's settings.

  • Ability to push to main is an access-control issue, not just documentation
  • Direct-push ratio measures commits landing on main without merge
  • Audit reveals gap between documented review process and actual commit behavior

Audit Force-Pushes and Rewritten History Without a Git Server

Rewritten history is the git equivalent of a locked room being opened from the inside: nothing in the working tree looks wrong, but the record of what happened has been changed.

  • Audit force-pushes require identification of rewritten history in remote repositories
  • gitpulse tools help detect deviations from baseline branch ratios and commit shapes
  • Weekly analytics and refactoring prioritization based on high-change hotspot files

More from Saturday 5 September →