ZeroHour

Search: “Content Credentials”

6,661 stories

Cyclops Blink Evolves Into x86-64 Linux Implant With Packet Sniffing and Internal Network Scanning

Sophos uncovers a new x86-64 Cyclops Blink Linux implant with packet sniffing and internal network scanning on compromised Cisco FMC appliances.

Sophos identified a 64-bit Linux Cyclops Blink implant in August on compromised Cisco Firewall Management Center devices, persisting via SysV init scripts and masquerading as the process 'kworker01'. The modular malware runs five child processes for reconnaissance, file transfer, scanning, packet capture, and persistence, and beacons hourly over outbound TLS to hardcoded C2 89.34.96.56 on ports 43856 and 49172. The family was previously tied to Russian-linked Sandworm activity on WatchGuard appliances, though Sophos treats 2026 attribution cautiously. The packet-capture module applies configurable filters to retain credentials, cookies, and authentication tokens from raw Ethernet traffic.

Cyber Security News · 2d agoMalware in the wild

AI "Mind Viruses" Can Spread Between Agents Through Persistent Prompt Files

Anthropic and EPFL researchers showed self-propagating payloads can spread between AI agents via persistent system-prompt files, though no in-the-wild spread was found.

A preprint released August 10, 2026 by Anthropic and EPFL researchers demonstrates that "mind virus" payloads can propagate between AI agents through persistent files such as SOUL.md and MEMORY.md that are injected into system prompts after context resets. In simulated agent chains modeled on OpenClaw, payloads stored in SOUL.md accounted for 88% of propagation attempts and succeeded 55% of the time, versus 17% success for ordinary workspace files; tested payloads ranged from crypto-ad text files to home-directory deletion. Susceptibility varied by model and configuration: Claude Sonnet 4.6 resisted and removed planted payloads, while DeepSeek V3.2, Qwen 3.5 32B, and Gemini 3 Flash adopted an ideological payload, and a one-paragraph warning in the system prompt reduced spread to near zero across 150+ adversarial payloads. No successful agent-to-agent propagation was found in the wild in archived Moltbook posts, and Anthropic's Frontier Red Team separately observed multiagent "turf wars" between unaware model instances sharing a codebase.

The Hacker News · 29d agoAI safety & security

How to secure edge AI in customer-owned environments

Microsoft outlines security architecture guidance for edge AI, urging runtime attestation, artifact provenance, and deterministic mediation of model actions.

Microsoft details how edge AI shifts trust responsibilities to customers operating their own infrastructure, where prompt injection, model tampering, and malicious firmware updates can occur alongside model weights, credentials, and physical-system access. The guidance recommends verifying runtimes with attestation, verifying AI artifacts with provenance, and constraining model actions through a deterministic mediator outside the model. It also covers new exposure surfaces from MCP, multi-agent systems, and computer-use agents running in disconnected or hostile edge environments.

Microsoft Security Blog · 12d agoAI safety & security