Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Phishing Site Tried to Talk to My AI. That Became the Evidence.

I wrote this piece for the purposes of entering Google's All Things Agentic Hackathon (Fortified Enterprise Fleet track). Somewhere in the HTML of a phishing page I built for testing, there is a line of text no human will ever see. It is written in Unicode Tag Characters — a block between U+E0000 and U+E007F that renders as nothing at all. Copy the page, paste it into a text editor, and you get…

The phishing site attempted to communicate with the investigating AI system using a hidden line of text written in Unicode Tag Characters. When this text was fed to a language model, it instructed the system to ignore previous instructions and redirect the abuse report to a different address. This malicious tactic aimed to deceive the agent investigating the phishing site.

The system was designed with cost efficiency in mind, using a multi-layered approach to investigate potential threats. The first layer used simple mathematical calculations, while the subsequent layers employed advanced AI models like Gemma triage and Gemini 3.5 Flash-Lite, with costs increasing as the layers progressed. The system aimed to minimize false negatives, ensuring that real threats were not missed, while also limiting false positives to reduce unnecessary investigation costs.

One of the key innovations in this system was the treatment of suspicious content as adversarial, preventing it from being concatenated into prompts or inserted into images. Additionally, the system ensured that the abuse contact information was validated, even if it came from a deterministic source like a registrar's RDAP response, as this field could be manipulated by attackers.

The system was built as a fleet of specialized agents on Google Cloud, designed to handle the vast volume of Certificate Transparency logs, investigate suspicious domains, and ultimately call a human for irreversible actions, such as initiating a takedown.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

g5g vs g6 for LLM Serving: the Same Code, and 3.7x the Throughput

This article compares two AWS GPU instance families for serving a small language model, using a payload that is byte-identical on both.

  • g5g.2xlarge and g6.2xlarge instances compared for LLM serving
  • g6.2xlarge shows 3.7x higher throughput than g5g.2xlarge
  • g5g suffers 87% decode-to-dtype conversion bottleneck

Gemma 4 in Pure JAX: What Changes Between Turing and Ada, and What Doesn't

This article is a measurement report on running a hand-written Gemma 4 port in pure JAX across two NVIDIA GPUs a generation apart, and on the two places the "it's just JAX" abstraction leaks.

  • Gemma 4 port runs in pure JAX on Turing and Ada GPUs
  • Compute dtype policy sets bfloat16 on both GPUs, causing performance hit on Turing
  • KV ring cache bug due to irregular Gemma 4 geometry prevents optimal port performance

More from Monday 31 August →