Notifications
Clear all
Topic starter
02/08/2026 12:25 pm
TL;DR: A FileFix campaign uses clipboard tricks, steganography, and PowerShell to deliver StealC, while Scattered Spider, Villager, and ShadowLeak show how social engineering, AI-enabled intrusion tooling, and AI agent abuse are widening the attack surface, according to Anomali. The common thread is that identity, browser, and agent trust boundaries are now being exploited faster than many controls can observe.
NHIMG editorial — based on content published by Anomali: Anomali Cyber Watch covering FileFix phishing, AI-driven pen-testing, the return of Scattered Spider, and related threats
By the numbers:
- 17 minutes., edentials are exposed publicly, attackers attempt access within an average of 17 minutes.
Questions worth separating out
Q: How should security teams reduce the risk of clipboard-based phishing leading to code execution?
A: Security teams should disable or restrict risky script paths, monitor for suspicious parent-child process chains, and train users that copy-and-paste into Explorer can execute commands.
Q: Why do browser-stored credentials increase the impact of infostealer malware?
A: Browsers often store session cookies, saved passwords, and cloud login artifacts in one place, so a single infostealer can unlock multiple accounts at once.
Q: What do security teams get wrong about AI agents connected to email or enterprise data?
A: They often assume the agent is only reading trusted content, when in reality the content itself can carry malicious instructions.
Practitioner guidance
- Harden user-to-code execution paths Block or tightly constrain PowerShell execution from user-driven paths such as Explorer, and alert on suspicious parent-child process chains that begin with file browsing.
- Treat browser sessions as sensitive identity assets Reduce dependence on saved browser credentials and session persistence for cloud and admin portals, especially on endpoints used for messaging and developer work.
- Verify every delegated identity reset out of band Require independent confirmation for password resets, MFA resets, and admin role changes, then log the approver, channel, and source of request for auditability.
What's in the full analysis
Anomali's full post covers the operational detail this analysis intentionally leaves for the source:
- Campaign-by-campaign IOCs and detection context for FileFix, Villager, and ShadowLeak.
- MITRE ATT&CK mappings for the specific intrusion stages and post-exploitation behaviours described in the source.
- Analyst commentary on why these campaigns are converging on identity, browser, and AI trust boundaries.
- The original roundup framing that situates each item in Anomali's current threat watch format.
👉 Read Anomali's roundup of FileFix phishing, AI-driven pentesting, and ShadowLeak →
FileFix phishing and browser credential theft: what should teams do now?
Explore further
02/08/2026 1:24 pm
Browser-stored credentials remain an under-governed identity layer: Stealers such as StealC target browser data because browsers now hold session state, saved credentials, and authentication artifacts that bypass many password hygiene assumptions. That makes the browser a credential warehouse, not just an endpoint application. IAM and PAM teams need to treat browser session material as privileged exposure, especially where cloud consoles and developer tools are accessible from the same profile.
A few things that frame the scale:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, according to LLMjacking: How Attackers Hijack AI Using Compromised NHIs.
- DeepSeek accidentally embedded over 11,000 secrets in its training data and left a database exposed online, revealing more than one million sensitive records including chat histories, backend credentials, and API keys, according to LLMjacking: How Attackers Hijack AI Using Compromised NHIs.
A question worth separating out:
A: They should revoke the affected sessions, rotate any exposed secrets, and review downstream access for privilege escalation or lateral movement. If the credential came from a browser or infostealer incident, assume the attacker may already have used it and move quickly to containment and authentication reset.
👉 Read our full editorial: FileFix phishing and AI-driven malware: why browser credentials are at risk
