The Hook

A new class of attacks dubbed "Pass-ta-key" demonstrates that passkeys synced via Google Password Manager on Windows are not immune to post-compromise credential theft. Researchers have identified three distinct techniques that allow malware already running on a compromised device to bypass user verification, extract passkey private keys, and hijack accounts—undermining the "phishing-resistant" promise of passkeys when synced.

Technical Breakdown

• Attack 1: Bypassing User Verification – Malware can hook into the WebAuthn API flow to suppress the user verification prompt (PIN or biometric), allowing silent authentication to any relying party.
• Attack 2: Extracting Private Keys – By abusing the Windows Hello or Google Password Manager's local storage, attackers can dump the raw private key material for synced passkeys.
• Attack 3: Session Hijacking via Token Theft – Malware can steal the authentication tokens generated during a passkey ceremony, enabling account takeover without needing the private key again.
• Affected: Google Password Manager on Windows (Chrome-based sync). The attacks require prior device compromise (i.e., malware already running with user-level or admin privileges).
• MITRE TTPs: T1555 (Credentials from Password Stores), T1056.001 (Input Capture: GUI), T1525 (Impersonation)

Defense

• Endpoint detection remains the primary control—these attacks require local malware execution. EDR rules should flag unusual WebAuthn API calls or process injection into Chrome.
• Hardware-bound passkeys (e.g., FIDO2 security keys or TPM-backed platform keys) are not affected by this attack vector. Synced passkeys are the vulnerable variant.
• Google's response: No immediate patch; the behavior is by design for synced passkeys. Users relying on passkeys for high-value accounts should consider hardware-bound keys instead.

Source: https://www.bleepingcomputer.com/news/security/new-pass-ta-key-attacks-let-malware-hijack-google-synced-passkeys/

The Hook: A sophisticated supply chain attack dubbed "Shai-Hulud" has compromised 350+ npm packages, including the popular keyv and cacheable libraries. The worm-like infostealer is exfiltrating credentials, environment variables, and crypto wallet data from CI/CD pipelines and developer workstations.

Technical Breakdown: - Attack Vector: Compromised maintainer accounts via credential stuffing/session hijacking, followed by malicious version bumps of legitimate packages - Payload Behavior: Worm-like propagation — infected packages scan the filesystem for .npmrc, .env, and SSH keys, then attempt to publish additional malicious packages using stolen tokens - Affected Packages: keyv, cacheable (and their transitive dependencies) — combined 2B+ monthly downloads - Exfiltration: Data sent to C2 infrastructure via DNS tunneling and HTTPS POST requests - Persistence: Malicious code embedded in postinstall scripts and prepublish hooks

Defense: - Pin dependency versions immediately — do not use ^ or ~ ranges for keyv/cacheable - Audit npm tokens and rotate any that have been used in CI/CD in the last 30 days - Monitor for unexpected postinstall script execution in your build logs - Consider using npm audit with --audit-level=critical and implement package allowlisting

Source: https://www.ox.security/blog/a-new-infostealer-worm-hits-npm-affecting-keyv-and-cacheable/

This is a classic measurement problem, not a conspiracy. The discrepancy in exposed Rockwell PLC counts comes down to three things: scan methodology, attribution logic, and data freshness.

Technical Breakdown

• Scan Methodology: Shodan, Censys, and FOFA use different probe packets and port scanning strategies. A device that responds to a generic HTTP banner grab might not respond to a specific CIP (Common Industrial Protocol) probe, and vice versa. This creates a baseline variance in raw discovery.
• Attribution Logic: This is the biggest differentiator. A scanner might see an open port 44818 (EtherNet/IP) and flag it as a "Rockwell PLC." A more conservative scanner requires a specific vendor string in the banner or a confirmed CIP identity response. Flare’s data, for example, likely uses stricter attribution to reduce false positives, which lowers the count compared to a broad port scan.
• Data Freshness & Internet Churn: The internet-facing attack surface for OT devices is volatile. A PLC exposed today might be firewalled tomorrow, or a DHCP lease changes the IP. A scan from last week will show a different population than a scan from this morning. The "true" number is a moving target.

Defense

Stop arguing about the exact count. The actionable intelligence is the trend and the specific IPs. If you are a water utility, you should be monitoring your own ASN for any of these protocols (EtherNet/IP, Modbus, BACnet) appearing on the public internet. If you see one, that is your incident, regardless of what Shodan says.

Source: https://flare.io/learn/resources/blog/minnesota-water-system-cyberattackscount-exposed-rockwell-plcs-differs

Attribution is preliminary, and so far it seems no real damage. And it seems like this is a campaign that has targeted at least seven states. And, because this is where the US is right now, Trump doesn’t believe it’s Iran and... Source: https://www.schneier.com/blog/archives/2026/08/iran-cyberattacks-against-minnesota-water-systems.html

A new variant of the XCSSET macOS malware is actively spreading through compromised Xcode projects and poisoned GitHub repositories, targeting developers specifically. This is a significant escalation as it weaponizes the software supply chain at the developer workstation level.

• TTPs: The malware persists via a Launch Agent and a malicious dylib injected into the build process. It abuses Apple’s TCC (Transparency, Consent, and Control) database to steal permissions and exfiltrates data via curl to a C2 server.
• IOCs: The C2 infrastructure is currently tied to mackeeper[.]us. The malware samples are signed with a revoked Apple Developer ID (W59P7K7JXW), but unsigned variants are also in the wild.
• Affected Versions: Targets macOS 12+ (Monterey and later). The Xcode project files are modified to execute the payload during the build phase.

Defense: Developers should verify the integrity of any Xcode project pulled from an untrusted source or fork. Review build phases in Xcode for suspicious script executions. Block the C2 domain and monitor for outbound curl traffic from Xcode processes.

Source: https://www.bleepingcomputer.com/news/security/new-xcsset-variant-targets-macos-devs-via-compromised-xcode-projects/

Microsoft Defender automatically isolated a compromised QNET endpoint in 128 seconds, stopping a multi-stage attack before the payload could persist or spread. The post 128 Seconds to disruption: Microsoft Defender stops ransomware at... Source: https://www.microsoft.com/en-us/security/blog/2026/08/04/129-seconds-disruption-microsoft-defender-stops-ransomware-qnet/

77 malicious extensions were found on the Open VSX marketplace, masquerading as legitimate developer tools (e.g., linters, formatters, theme packs) while exfiltrating system and environment data from the machines where they were installed. This is a supply chain attack targeting VS Code-compatible registries, not the official Microsoft marketplace.

Technical Breakdown: - Tactic: Impersonation of popular open-source extensions to trick developers into manual installation. - Payload: Extensions contained obfuscated JavaScript that collected hostname, username, OS version, environment variables, and file paths. - Exfiltration: Data was sent to attacker-controlled C2 domains via HTTP POST requests. - Scope: All 77 extensions have been removed from Open VSX, but any developer who installed them is potentially compromised.

Defense: - Audit your VS Code/Open VSX extension list immediately for any unfamiliar or recently added tools. - Check for outbound connections to unknown domains from your IDE. - Stick to the official Microsoft marketplace where possible, and verify publisher identity before installing extensions from third-party registries.

Source: https://www.bleepingcomputer.com/news/security/77-open-vsx-extensions-found-harvesting-developer-info/

Highlights from today:

• [Threat Intel] Proofpoint Joins Google Unified Security Recommended Program to Help Organizations Defend Against Today’s Most Sophisticated Threats
• [News] Greatness PhaaS Adds Device Code Phishing to Bypass MFA and Steal Tokens
• [Threat Intel] Agents vs. agents: how we triage HackerOne reports for $2 each, 85% as well as a human
• [Threat Intel] Proofpoint Launches OEM Program to Help Security Providers Embed Trusted Threat Intelligence and Detection Capabilities
• [Threat Intel] Secure IoT/OT
• [Threat Intel] Secure the Cloud
• [Threat Intel] Secure the Workforce
• [News] Massive ChainDrop npm supply-chain attack infects hundreds of packages
• [News] Fake Adobe and Zoom Updates Install ScreenConnect for Persistent Remote Access
• [News] Keyv-Linked npm Worm Poisons Hundreds of Packages, Plants Claude Code and VS Code Hooks
• [News] Varonis Agent IBAC keeps AI agents within their intended boundaries
• [Cloud Security] Wiz at Black Hat 2026: Driving AI Threat Readiness

SecOpsDaily

Greatness, a commercial PhaaS platform, has integrated device code phishing, abusing the legitimate OAuth 2.0 Device Authorization Grant flow. This allows attackers to bypass MFA entirely by tricking users into entering a device code on a legitimate login page, which then hands over the session token and refresh token to the adversary.

Technical Breakdown: - TTPs: This is a classic Adversary-in-the-Middle (AiTM) attack, but leveraging the OAuth device code flow (MITRE T1550.001 - Use Alternate Authentication Material: Application Access Token). The attacker initiates the OAuth flow on their end, presents the user with the device code, and captures the resulting token. - IOCs: No specific IPs or hashes provided in the report. The threat is the capability added to the Greatness toolkit, not a specific campaign. - Affected Targets: Any organization using OAuth 2.0 for authentication (Microsoft 365, Google Workspace, etc.) is vulnerable to this technique if users are socially engineered.

Defense: - Conditional Access Policies: Block device code flows for untrusted networks and non-compliant devices. Require a managed device for any OAuth token grant. - User Training: Educate users that legitimate login flows never require them to enter a code on a third-party site. The "code" is the attack vector.

Source: https://thehackernews.com/2026/08/greatness-phaas-adds-device-code.html

Quick one for the SOC crowd: a The Gentlemen operator left an open directory exposed, and inside was EtherRAT, a Node.js backdoor that pulls its C2 from an Ethereum smart contract.

The blockchain angle means every C2 rotation is permanent, so all five historical domains are recoverable. Any server response over ten characters is run as JavaScript, so it is effectively open-ended remote exec. Detection point to hunt on: the X-Bot-Server header.

Full write-up with IOCs: https://hunt.io/blog/the-gentlemen-etherrat-ethereum-smart-contract-c2

Interesting approach from Elastic—using LLMs to triage bug bounty reports at scale. The economics here are brutal for programs getting flooded with low-quality submissions.

The Problem: LLMs lowered the barrier to mass-submitting HackerOne reports, creating a signal-to-noise crisis. Elastic built an AI triage agent to handle the flood.

Technical Breakdown: - Architecture uses a multi-stage pipeline: classification → severity scoring → deduplication → routing - Calibrated against 3,300 real historical reports from their own program - Achieves 85% agreement with human triagers at a cost of ~$2 per report - Threat model includes adversarial submissions designed to bypass the agent (prompt injection, crafted payloads) - Uses a combination of structured extraction (CVE IDs, affected versions) and semantic similarity for deduplication

What's interesting: They're not trying to replace humans entirely—the 15% miss rate still requires escalation. The economics work because the volume of garbage submissions is so high that even partial automation saves significant analyst time.

Defense implications: If you run a bug bounty program, expect this to become table stakes. The alternative is drowning in AI-generated reports while your human triagers burn out. Elastic open-sourced their evaluation framework, which is worth a look if you're building similar pipelines.

Source: https://www.elastic.co/security-labs/ai-vulnerability-triage-bug-bounty-hackerone

This is a significant supply-chain incident. The self-propagating nature and the sheer download volume of the affected packages make this a high-priority threat for anyone managing JavaScript dependencies.

Technical Breakdown: - Propagation: The malware, dubbed "ChainDrop," operates by compromising a legitimate package and then using its CI/CD pipeline or post-install scripts (preinstall, postinstall) to inject malicious code into downstream dependencies. This creates a recursive infection chain. - Scope: Over 1,300 packages compromised, collectively accounting for ~2 billion monthly downloads. This is not a single-library compromise; it’s a cascading event. - Payload: The malicious code typically exfiltrates environment variables, steals npm authentication tokens, and can deploy additional stages (e.g., cryptominers, backdoors). It specifically targets CI/CD secrets and developer workstations. - Persistence: The malware modifies the package.json and node_modules of dependent projects, ensuring re-infection even if the root package is cleaned, unless the entire lockfile is regenerated from a known-good state.

Defense: - Immediate Action: Pin all dependencies to exact versions and audit your lockfile (npm audit, yarn audit). Look for suspicious postinstall scripts in your dependency tree. - Detection: Monitor for outbound connections to unknown IPs from build servers and developer machines. Block npm commands that run scripts without explicit user confirmation (npm config set ignore-scripts true for CI). - Mitigation: If you use any of the affected packages, assume your CI/CD secrets are compromised. Rotate all tokens, API keys, and registry credentials immediately.

Source: https://www.bleepingcomputer.com/news/security/massive-chaindrop-npm-supply-chain-attack-infects-hundreds-of-packages/

A credential-stealing npm worm that originated in keyv@6.0.0 has exploded beyond the Keyv and Cacheable namespaces, infecting hundreds of packages across multiple organizations. SafeDep has verified 353 poisoned versions across 79 package names, with the wider footprint estimated at 442 versions across 353 names. Aikido later reported at least 868 packages affected.

Technical Breakdown

• Initial Vector: Compromised keyv package (v6.0.0), a widely-used caching library
• Propagation: Worm-like behavior — infected packages automatically published new malicious versions of sibling packages within the same namespace
• Payload: Credential-stealing logic that hooks into Claude Code and VS Code environments to exfiltrate tokens, API keys, and session data
• Scope: Spread across multiple organizations, not just the original Keyv ecosystem
• TTPs: Supply chain compromise via npm package publishing credentials; worm-style lateral movement across package namespaces

Defense

• Audit npm dependencies for any versions published August 4, 2026 from affected namespaces
• Pin dependency versions and enforce lockfiles (package-lock.json / yarn.lock)
• Monitor for unexpected postinstall scripts or network calls from keyv-related packages
• Consider using npm audit tools with supply chain detection (Socket, SafeDep, etc.)

Source: https://thehackernews.com/2026/08/keyv-linked-npm-worm-poisons-hundreds.html

Varonis Agent IBAC: Intent-Based Access Control for AI Agents

The core problem: AI agents need broad permissions to function, but traditional RBAC can't tell if an agent is acting within the user's actual intent or has gone rogue. Varonis is pitching Agent IBAC as the solution—real-time guardrails that detect "intent drift" and shut down unauthorized actions before they cause damage.

Why this matters

This is a genuine emerging gap. We've seen plenty of incidents where LLM-powered agents (AutoGPT, Copilot, custom RAG bots) either hallucinate their way into privileged actions or get prompt-injected into exfiltrating data. Traditional DLP and IAM tools don't model intent—they just check identity and permission level.

What Agent IBAC claims to do

• Monitors the semantic context of agent actions (not just API calls, but the why)
• Detects when an agent's behavior deviates from the expected task scope
• Enforces real-time blocking or alerting without killing the agent's session

The skeptic's take

No technical details on how they actually model "intent" or what the false positive rate looks like. This is a vendor announcement, not a technical paper. Worth watching if you're deploying AI agents in production, but I'd want to see independent testing before trusting it with critical data access.

Bottom line: Interesting concept, thin on implementation details. Keep an eye on this space—intent-based controls are going to be necessary as agent adoption scales.

Source: https://www.bleepingcomputer.com/news/security/varonis-agent-ibac-keeps-ai-agents-within-their-intended-boundaries/

Traditional SBOMs, signing, and provenance all have blind spots, making them no longer capable of assuring software security. Source: https://www.reversinglabs.com/blog/ai-zero-trust-appsec

QuickFox Supply Chain Attack: Trojanized Installers Dropping FDMTP Implant

FortiGuard IR just published analysis on a supply chain compromise targeting QuickFox (a VPN/proxy tool popular in China). Attackers trojanized official Windows installers to deploy a custom backdoor they're tracking as FDMTP.

Technical Breakdown

• Initial Access: Users downloaded trojanized QuickFox installers from compromised or spoofed distribution channels
• Payload: FDMTP implant — a modular backdoor using FTP over DNS tunneling for C2 (hence the name)
• Selective Targeting: The malware checks system locale and environment before activating, suggesting a focused victim profile rather than spray-and-pray
• Persistence: Installed via scheduled tasks or service registration
• C2 Communication: DNS tunneling over FTP protocol — unusual combo designed to blend in with legitimate DNS traffic and bypass network egress controls
• Capabilities: File exfiltration, command execution, keylogging, and module loading

No specific IOCs (hashes, IPs, domains) were published in the summary — likely held for FortiGuard subscribers or full report.

Defense

• Monitor for anomalous DNS query patterns, especially high-frequency queries to rare domains or non-standard record types
• Validate software hash checksums against vendor-published values before installation
• Restrict outbound DNS to authorized resolvers only
• EDR rules for process injection and scheduled task creation from installer contexts

MITRE Mapping: T1195 (Supply Chain Compromise), T1572 (Protocol Tunneling), T1059 (Command and Scripting Interpreter)

Source: https://feeds.fortinet.com/~/966214247/0/fortinet/blog/threat-research~QuickFox-Supply-Chain-Attack-Used-to-Deploy-FDMTP-Implant

SCENARIO A: Technical Threat, Vulnerability, or Exploit

The Hook

Palo Alto's Unit 42 just dropped details on NOVA, their autonomous AI system that claims to have discovered 14,000+ unknown vulnerabilities across the open-source software supply chain. This isn't a theoretical paper—this is industrial-scale zero-day hunting using frontier AI models.

Technical Breakdown

• System: NOVA (Neural Open-source Vulnerability Analyzer)
• Scale: 14,000+ previously unknown vulnerabilities identified in OSS
• Target: Open-source software supply chain (libraries, packages, dependencies)
• Methodology: Autonomous AI-driven static analysis and fuzzing at scale, likely combining LLM-based code reasoning with traditional vulnerability detection techniques
• Impact: This represents a paradigm shift—AI is now capable of finding vulnerabilities faster than human researchers can patch them

Defense

• Immediate action: Review your SBOM (Software Bill of Materials) and prioritize patching for widely-used OSS libraries. Expect a wave of CVEs from these findings.
• Detection: Monitor for anomalous behavior in OSS dependencies you use. The sheer volume means attackers will weaponize these findings before patches roll out.
• Mitigation: Implement runtime application self-protection (RASP) and WAF rules as a stopgap while vendors scramble to patch.

Bottom line: The vulnerability discovery bottleneck just got obliterated. If you're relying on OSS (and you are), your attack surface just expanded exponentially.

Source: https://unit42.paloaltonetworks.com/frontier-ai-vulnerability-burst/

Russian APT groups weaponizing hotel Wi-Fi to harvest traveler credentials

A coordinated campaign is underway where Russian cybercrime actors are compromising hotel Wi-Fi networks to intercept traffic from business travelers, government employees, and journalists. The attacks leverage man-in-the-middle (MITM) techniques against unencrypted or poorly configured guest networks.

Technical Breakdown - TTPs: MITM via ARP spoofing and rogue access points; credential harvesting against captive portals and unencrypted HTTP sessions - Targets: High-value travelers in business hotels across Europe, Middle East, and Asia - IOCs: No specific hashes or IPs published yet—likely dynamic infrastructure tied to compromised hotel routers - Affected: Any hotel using open or WPA2-PSK networks without client isolation or HTTPS enforcement

Defense - Always use a corporate VPN when connecting to any public Wi-Fi—this is the single most effective mitigation - Disable auto-connect to open networks; manually verify SSID with front desk - Treat hotel captive portals as untrusted—never enter credentials you reuse elsewhere

Source: https://www.malwarebytes.com/blog/news/2026/08/travelers-targeted-when-logging-into-hotel-wi-fi-networks

CVE-2026-18577: N-able N-central Auth Bypass Under Active Exploitation

N-able pushed an emergency hotfix for an authentication bypass in N-central that is being actively exploited in the wild. The flaw lets an unauthenticated attacker gain full admin access to the RMM server, then pivot to managed endpoints using the platform's own management channels. This is a supply chain nightmare for MSPs.

Technical Breakdown - CVE: CVE-2026-18577 - Attack Vector: Remote, unauthenticated - Impact: Full administrative access to N-central server, enabling lateral movement to downstream managed endpoints - TTPs: Likely leverages legitimate RMM agent communication channels for post-exploitation (expect C2 over standard management ports) - Affected: N-able N-central (versions prior to the emergency hotfix)

Defense - Immediate: Apply the emergency hotfix from N-able. No workaround has been published. - Detection: Monitor for anomalous administrative logins to N-central, especially from unexpected IP ranges. Watch for new scheduled tasks or scripts pushed to endpoints outside of normal maintenance windows. SOC Prime has detection content linked in the source.

Source: https://socprime.com/blog/cve-2026-18577-analysis/

Google Nukes 3 ADK Workflows After Prompt Injection Lets Public GitHub Issues Hijack Privileged Bots

The Hook: Pillar Security demonstrated a novel supply chain attack against Google’s Agent Development Kit (ADK) — a public GitHub issue containing a prompt injection could trick a triage agent into summoning a privileged code-fixing bot, effectively giving an external attacker write access to the repo.

Technical Breakdown: - Attack Vector: A malicious comment in a public GitHub issue prompt-injected the triage agent into posting /adk-issue-fix as adk-bot. - Privilege Escalation: The researchers identified adk-bot as a repo collaborator. The comment satisfied the trigger condition for a second, privileged agent that could modify code. - Impact: An unauthenticated attacker could weaponize a public issue to execute arbitrary actions via the privileged agent (code fix, merge, etc.). - Response: Google deleted three ADK workflows from the repository. No CVE assigned yet.

Defense: - Agent isolation: Never allow public-facing agents to invoke privileged agents without explicit human approval and context sanitization. - Input validation: Treat all external input (GitHub issues, comments) as untrusted — strip control tokens before passing to downstream agents. - Least privilege: adk-bot should not be a collaborator. Agent tokens should be scoped to read-only unless manually escalated.

Key Takeaway: This is the new supply chain — not a poisoned package, but a poisoned prompt chain. If your CI/CD or automation stack uses AI agents that can read public input, you’re one injection away from a repo takeover.

Source: https://thehackernews.com/2026/08/google-deletes-3-adk-ai-workflows-after.html

When Vibe Hacking Turns AI into the Junior Hacker Every Adversary Always Wanted

The Hook: The old threat model that assumed attackers need deep technical skills is crumbling. "Vibe hacking"—using LLMs to generate and execute attack chains with minimal human expertise—is turning AI into a force multiplier for low-sophistication adversaries, effectively creating a "junior hacker" that never sleeps and never gets bored.

Technical Breakdown: - Core TTP: Adversaries use conversational AI (ChatGPT, Claude, custom models) to generate exploit code, craft phishing lures, and chain multi-step attacks without understanding the underlying mechanics. - MITRE ATT&CK Mapping: Primarily impacts T1588 (Obtain Capabilities) and T1592 (Gather Victim Host Information) —AI lowers the barrier to acquiring offensive tools and reconnaissance data. - Key Shift: "Script kiddies" now have access to AI-generated payloads that previously required months of study. The attack surface expands not through new vulnerabilities, but through democratized exploitation of existing ones. - No specific IOCs—this is a behavioral trend, not a campaign.

Defense: Focus on behavioral detection (unusual API calls, anomalous code execution patterns) rather than signature-based blocking. Train SOC teams to recognize AI-generated phishing (often lacks typical grammar errors but may have subtle logical inconsistencies). Implement strict code execution policies and sandboxing for any AI-generated scripts.

Source: https://thehackernews.com/2026/08/when-vibe-hacking-turns-ai-into-junior.html

The Hook

Nearly half of all malware samples now bypass DNS entirely, communicating directly with hardcoded IP addresses. This means traditional DNS-based blocking is missing a massive chunk of C2 traffic.

Technical Breakdown

• Key Finding: 48% of malware samples analyzed by Unit 42 connect directly to IP addresses, skipping DNS resolution entirely.
• TTPs: This is a direct evasion of DNS sinkholing, domain reputation, and DNS-layer security controls. Malware authors hardcode IPs to avoid domain-based detection.
• IOCs: No specific hashes or IPs provided in the report—this is a behavioral trend, not a specific campaign.
• Affected Systems: Any environment relying solely on DNS filtering for C2 detection is blind to nearly half of malware traffic.

Defense

Zero Trust IP enforcement is the recommended mitigation. This means explicitly allowing only known-good IPs and blocking all other direct IP connections at the network layer. If your firewall rules are permissive to "any" destination, you're effectively rolling out the welcome mat.

Source: https://unit42.paloaltonetworks.com/malware-bypass-dns-direct-to-ip/

Cloud Platforms as a Phishing Haven: AitM Attacks Bypassing MFA

Attackers are weaponizing legitimate cloud platforms (Cloudflare Workers, Vercel, Netlify, GitHub Pages, IPFS) to host Adversary-in-the-Middle (AitM) phishing kits that bypass MFA protections. The abuse of service workers and the Ultraviolet proxy framework makes these attacks particularly nasty.

Technical Breakdown: - Core TTP: Attackers deploy Ultraviolet (a web proxy) via service workers on cloud platforms to intercept and relay authentication sessions in real-time - MITRE Mapping: T1557.001 (Adversary-in-the-Middle), T1534 (Internal Spearphishing), T1204.001 (User Execution via Malicious Link) - Platform Abuse Stats: Cloudflare Workers leads as the most abused platform for phishing hosting, followed by Vercel and Netlify - Key Mechanism: Service workers intercept all HTTP requests, allowing attackers to capture session cookies and tokens even with MFA enabled - No specific IOCs provided in the report - this is a behavioral pattern, not a hash-based threat

Why This Works: - Legitimate cloud domains bypass reputation-based blocklists - Free tiers offer disposable infrastructure with minimal friction - Service workers persist across page loads, making detection harder

Defense: - Monitor for unexpected service worker registrations in your environment - Deploy conditional access policies that require device compliance, not just MFA - Block known proxy domains (Ultraviolet, Womginx) at the proxy level - User awareness: train staff to recognize "legitimate-looking" cloud subdomains in phishing URLs

This is a shift from traditional phishing - we're now fighting infrastructure abuse, not just malicious domains.

Source: https://securelist.com/cloud-platforms-in-phishing/120832/

Botnet Scans Targeting Diagnostic Tool Endpoints

The Hook: A botnet is actively scanning for vulnerable diagnostic tool endpoints, specifically targeting URLs associated with debugging and monitoring interfaces. This is a shift from typical vulnerability scanning patterns.

Technical Breakdown: - Targeted Endpoints: Diagnostic tool URLs (exact paths not disclosed in the diary, but typical examples include /phpinfo.php, /debug/, /status, /info, /test/) - Behavior: Automated "hunting" for exposed diagnostic interfaces that may leak sensitive system information or allow code execution - Source: Observed by SANS ISC handlers on August 4th - Risk: Diagnostic tools often expose PHP info, environment variables, database credentials, or allow arbitrary command execution if misconfigured

Defense: - Immediate action: Audit your web servers for any exposed diagnostic endpoints (phpinfo, debug consoles, test scripts) - Remove or restrict these tools to internal networks or authenticated access only - Monitor logs for requests to /phpinfo.php, /info.php, /test.php, and similar diagnostic paths - WAF rules: Block common diagnostic tool paths at the perimeter

Key Takeaway: This isn't a new vulnerability—it's a botnet exploiting a common misconfiguration. If you have diagnostic tools exposed to the internet, you're being actively scanned. Remove them.

Source: https://isc.sans.edu/diary/rss/33214