cd /news/ai-safety/symantec-watches-ai-written-scripts-… · home › topics › ai-safety › article
[ARTICLE · art-172049] src=security.com ↗ pub= topic=ai-safety verified=true sentiment=↓ negative

Symantec watches AI-written scripts restart a stalled retail intrusion

Symantec reconstructed a September 2026 intrusion at a US retailer in which an attacker's hand-typed commands failed repeatedly until the operator switched to an AI tool, after which roughly 50 scripts arrived in two hours with a median length above 500 characters and no typos. On 21 and 22 September the attacker made 110 actions averaging about 45 characters per command, mistyping systeminfo and pwoershell and re-running the same blocked loader five times; gaps between submissions never fell below seven seconds, which Symantec read as a person relaying output rather than an autonomous agent. The attacker eventually worked across seven servers, most running SQL Server, searched point-of-sale scripts for stored passwords, and Symantec linked the infrastructure to an August intrusion and a July breach at a securities firm, neither of which showed AI use, with no data theft or encryption observed.

recommendation

Treat sub-seven-second, typo-free script bursts with labelled output sections as human-relayed AI activity, and audit SolarWinds Orion bundled components and point-of-sale scripts for stored credentials before an operator pivots across servers.

more in playbook: Securing agents and AI tools
read1 min views12 publishedNov 12, 2026

Symantec reconstructed a September 2026 intrusion at a US retailer where hand-typed commands kept failing until the operator switched to an AI tool. On 21 and 22 September the attacker made 110 actions, averaged about 45 characters per command, mistyped systeminfo and pwoershell, and re-ran the same blocked five times. The next day brought roughly 50 scripts in two hours, with a median length above 500 characters, no typos, labelled output sections, error handling and comments that read like a model reasoning through earlier failures. Gaps between submissions never fell below seven seconds, which Symantec read as a person relaying output rather than an autonomous agent. About ten minutes after querying SolarWinds Orion, the attacker used a bundled component to run commands on a second server, and eventually worked across seven servers, most running SQL Server. They searched point-of-sale scripts for stored passwords. Symantec linked the infrastructure to an August intrusion and a July breach at a securities firm, neither of which showed AI use, and saw no data theft or encryption.

── more in #ai-safety 4 stories · sorted by recency
── more on @symantec 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/symantec-watches-ai-…] indexed:0 read:1min 2026-11-12 · —