A high-severity unpatched security flaw in Langflow, an open-source low-code platform to build artificial intelligence (AI) applications, has come under active exploitation in the wild, according to findings from VulnCheck. The vulnerability in question is CVE-2026-5027 (CVSS score: 8.8), a case of path traversal that could allow an attacker to write files to arbitrary locations. "The 'POST /
Cybersecurity News and Vulnerability Aggregator
Cybersecurity news aggregator
Updated: 9:00 pm
J/K Navigate / Search S Save V Open Link
— or
treemd <(curl -sL https://allsec.sh/md) (as Markdown) Top Cybersecurity Stories Today
Microsoft has patched an actively exploited Exchange Server vulnerability that allows threat actors to execute arbitrary JavaScript code in cross-site scripting (XSS) attacks targeting Outlook Web Access users. [...]
Microsoft warned customers on Tuesday that they may have issues installing the latest monthly updates on some Windows devices that were upgraded to Windows 11 24H2 or 25H2. [...]
The Miasma credential-stealing attack framework, which has recently targeted open-source ecosystems through supply-chain attacks, was briefly open-sourced on GitHub. [...]
Cybersecurity researchers have warned of a "resurgence and expansion" of JDY, a covert network associated with China-nexus state-sponsored threat actors. "The JDY botnet comprises over 1,500 SOHO [small office and home office] and IoT devices and operates as a centrally controlled, high-performance scanner used to discover, fingerprint, and continuously map exposed services at scale," Lumen's
Latest
Wednesday, June 10
US lawmakers are alarmed that Bill Pulte, a housing official with no intelligence experience, is poised to take charge of one of the government's most powerful surveillance tools.
The Miasma credential-stealing attack framework, which has recently targeted open-source ecosystems through supply-chain attacks, was briefly open-sourced on GitHub. [...]
GitHub has announced that npm v12, expected next month, will introduce several security-focused changes aimed at blocking supply-chain attacks abusing behaviors triggered by the 'npm install' command. [...]
Pre-auth XXE → HTTP SSRF on ArubaOS 8.13.2 closed as "theoretical / no valid PoC" despite TCP pcap, sshd localhost log, and internal port scan — documenting for community review
Pre-auth XXE on ArubaOS 8.13.2 port 32000 (default-xml-api, no auth required). Evidence: TCP pcap + sshd [127.0.0.1](http://127.0.0.1) log + 9 internal ports via SSRF. Closed as "theoretical / no valid PoC." Full writeup + PoC + pcap on GitHub.
Oracle PeopleSoft servers are being targeted in ongoing data theft attacks by the ShinyHunters extortion gang, which claims to have stolen data from over 100 organizations. [...]
On affected platforms running Arista EOS where a tunnel decapsulation configuration—such as VXLAN (Virtual Extensible LAN), decap-groups, or a GRE (Generic Routing Encapsulation) tunnel interface—is present, the switch will incorrectly decapsulate and forward other unexpected tunneled packet
The curl project, one of the most important pieces of software on the internet, just shut down its bug bounty program. Not because the project is less important. Not because the community gave up. But because 95% of the vulnerability reports it received were not valid. About a fifth were outright AI-generated noise. Only around […] The post Nobody’s in the Cockpit: The Real Risk of Fully Autonomous AI Security Testing appeared first on Synack .
I think we finally have something that everybody expected from CISA to clarify: CISA has released BOD 26-04, and it marks a major turning point in how the federal government handles vulnerability management. For those that are not familiar... for years it has been obvious that patching driven solely by CVSS scores does not work. A high score triggered an urgent fix AND A low score got pushed down the queue, most of the time... indefinitely. That model takes no account of how attackers operate in practice, and it ignores the inconsistent quality of data across the CVE ecosystem. BOD 26-04 formalizes a framework that ranks vulnerabilities by actual risk, built around four signals that genuinely matter: \- Asset exposure: is the vulnerable system reachable from the public internet? \- KEV status: is the vulnerability already confirmed as exploited in the wild? \- Exploit automation: can an adversary script the complete attack chain? \- Technical impact: does successful exploitation give the attacker partial or total control of the asset? The result is a prioritization model that reflects risk as it exists in practice rather than theoretical severity. Agencies can at last defer vulnerabilities that present minimal danger and concentrate their resources where the data demonstrates they matter most. So from what I understand: Patch volume is not a security strategy, but context grounded in data is. I would say, finally? Should have been for the last 10y like that already.
Cybersecurity researchers have warned of a "resurgence and expansion" of JDY, a covert network associated with China-nexus state-sponsored threat actors. "The JDY botnet comprises over 1,500 SOHO [small office and home office] and IoT devices and operates as a centrally controlled, high-performance scanner used to discover, fingerprint, and continuously map exposed services at scale," Lumen's
Fortinet, Ivanti, and SAP have released security updates to address multiple critical security vulnerabilities that could result in arbitrary code execution and information disclosure. The security flaw patched by Fortinet relates to a command injection vulnerability in FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS WEB UI. It's tracked as CVE-2026-25089 (CVSS score: 9.1). "An
A high-severity unpatched security flaw in Langflow, an open-source low-code platform to build artificial intelligence (AI) applications, has come under active exploitation in the wild, according to findings from VulnCheck. The vulnerability in question is CVE-2026-5027 (CVSS score: 8.8), a case of path traversal that could allow an attacker to write files to arbitrary locations. "The 'POST /
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Tuesday added three new vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, following reports of active exploitation. The list of vulnerabilities is as follows - CVE-2026-20245 (CVSS score: 7.8) - An improper encoding or escaping of output vulnerability in Cisco Catalyst SD-WAN Manager that could allow an
Attackers are increasingly bypassing weak authentication through phishing, MFA fatigue, and service desk social engineering. Specops Software breaks down five best practices for stronger identity verification and access security. [...]
A cybercrime group known as The Gentlemen has emerged as the second most active ransomware gang by victim count, rapidly attracting a talented pool of hackers through an aggressive recruitment strategy that promises affiliates 90 percent of any ransom paid by victims. This post examines clues pointing to a real life identity for the administrator of The Gentlemen ransomware group. A graphic created and shared by The Gentlemen ransomware group administrator Hastalamuerte on Breachforums in May 2026. Credit: ke-la.com. Experts at the security firm Check Point Software have been closely covering exploits of The Gentlemen, a so-called “ransomware-as-a-service” (RaaS) offering that pays affiliates handsomely to help spread the group’s malware. “A 90/10 affiliate revenue split — compared to the industry standard 80/20 — is accelerating the group’s growth by attracting experienced operators from competing programs,” the researchers wrote in April. Check Point found The Gentlemen are the second most active ransomware group by victim count so far this year, claiming at least 332 published victims since the group’s inception in mid-2025 and more than 240 in 2026 alone. According to Check Point, the group targets Internet-facing devices (VPNs, firewalls) as their entry point, and once inside moves quickly to encrypt entire networks within hours. Check Point says the administrator and primary operator of th
The ACLU is suing two Florida police departments over the arrest of a Fort Myers man in a child-abduction case, saying officers treated a flawed face-recognition match as a near-certain ID.
Microsoft has patched an actively exploited Exchange Server vulnerability that allows threat actors to execute arbitrary JavaScript code in cross-site scripting (XSS) attacks targeting Outlook Web Access users. [...]
Especially relevant on systems processing PKCS#7 or S/MIME contents https://nvd.nist.gov/vuln/detail/CVE-2026-45447
Microsoft warned customers on Tuesday that they may have issues installing the latest monthly updates on some Windows devices that were upgraded to Windows 11 24H2 or 25H2. [...]
[https://securityaffairs.com/193393/security/frances-government-messaging-app-tchap-got-breached.html](https://securityaffairs.com/193393/security/frances-government-messaging-app-tchap-got-breached.html)
Most US World Cup stadiums are surrounded by surveillance cameras. Want to know if you’re being watched on your way to a match? These maps will help you.
From anti-drone tech to face recognition, 2026 World Cup stadiums in the US, Canada, and Mexico are subjecting fans to an array of surveillance tech. Here’s what you need to know.
The organization claims that the FIFA tournament could have impacts on the rights of local people and visiting soccer fans in all three host countries.
certSIGN: Inconsistent revocation status (CRL "revoked" vs OCSP "good") for intermediate CA "certSIGN Web CA"
certSIGN seems to have revoked a commonly-used intermediate cert. At least their CRL seems to say that.
Cybersecurity failures now happen beyond the OSI stack. Faulty governance, the human factor, and AI tools create new attack surfaces. After seven years working across cybersecurity, cloud infrastructure, and Zero Trust architecture, Jayal Yadav explains how we got here and what organizations still get wrong. “The original seven layers of the OSI model still matter. […] The post The OSI Model and Its Two Missing Layers appeared first on Heimdal Security Blog .
On June 9, Anthropic released Claude Fable 5, the most capable model it has ever made, generally available. It also did something unusual: it shipped one model as two products, split not by capability but by a layer of safety classifiers. Fable 5 goes to the public. Its twin, Claude Mythos 5, the same underlying model with the cyber safeguards lifted, stays locked to a vetted group of cyber
GhostTrace – a Windows forensic scanner that finds what "Uninstall" leaves behind (22 modules, read-only, offline)
I built a CLI tool for Windows that investigates software remnants across 22 forensic modules in a single pass. The problem it solves: after uninstalling software, Windows rarely cleans everything. Registry keys, prefetch entries, scheduled tasks, WMI subscriptions, BAM/DAM timestamps and more often stay behind. GhostTrace finds all of it in one scan. **Forensic coverage:** * **Persistence (MITRE ATT&CK TA0003):** Run/RunOnce keys, services with suspicious ImagePath (T1543.003), IFEO debugger, AppInit\_DLLs, LSA packages, scheduled tasks via Task Scheduler COM API, WMI EventFilter/Consumer bindings (T1546.003), Ghost Tasks in TaskCache\\Tree (T1053.005) * **Execution evidence (TA0002):** Shimcache/AppCompatCache, Prefetch with XPRESS-Huffman decode (versions 26/30/31), BAM/DAM with per-SID last-run timestamps, UserAssist (ROT13 decoded), MUICache * **User activity:** PowerShell history with cradle/encoded payload detection (T1059.001), RDP outbound history (T1021.001), RecentDocs, USB device history via USBSTOR (T1052/T1091), network artifacts (hosts redirects + connected networks with dates) * **Installed software and disk residue:** Uninstall entries with publisher/path/uninstall string, startup approved state, filesystem trace in Program Files/ProgramData/AppData **Design decisions relevant to forensics:** * Read-only by default — scan never modifies anything * Execution caches and history are excluded from cleanup — evidence is preserved * Cleanup requires explicit typed confirmation * Zero network calls, zero telemetria — safe in air-gapped environments * Suspicious signal is data for analysis, not an automatic verdict * Each cleanup generates an audit log **Stack:** C# · .NET 10 · Spectre.Console · Windows 10/11 x64 Download: [github.com/Devzinh/GhostTrace](https://github.com/Devzinh/GhostTrace) Happy to answer questions about the forensic modules or implementation decisions.
Ivanti has patched two critical vulnerabilities in its Sentry secure mobile gateway solution, including a maximum-severity flaw that enables remote attackers to execute code with root privileges. [...]
Presently sponsored by: Report URI: Guarding you from rogue JavaScript! Don’t get pwned; get real-time alerts & prevent breaches #SecureYourSite 1,000 breaches is one hell of a milestone. It's not just the process of getting data, verifying it, loading it, sending notifications etc, it's all the other stuff that goes into keeping the whole thing afloat. Legal docs. Trademarks. Accounting. Agreements. The most mind-numbingly boring stuff you can imagine happening in the background so that the stuff you see in the foreground can all work. And then there are those "other things" I had to deal with along the way, but more of that in this week's video. Thanks to everyone who has stuck around to see this thing reach such a milestone
Cybersecurity researchers have flagged half a dozen vulnerabilities in protobuf.js, a JavaScript and TypeScript implementation of Protocol Buffers (Protobuf), that, if successfully exploited, could result in remote code execution (RCE) and denial-of-service (DoS) attacks. "In affected environments, a single malicious protobuf schema, descriptor, or crafted payload could be enough to trigger
Tuesday, June 9
Microsoft today released software updates to plug nearly 200 security holes across its Windows operating systems and supported software, a record number of fixes for the company’s monthly Patch Tuesday cycle. Nearly three dozen of those bugs earned Microsoft’s most dire “critical” rating, and exploit code for at least three of the weaknesses is now publicly available. The software giant said in a blog post last month that both its engineers and the security community are increasing using artificial intelligence tools to find bugs, meaning this month’s heavy Patch Tuesday may start to become the norm, said Satnam Narang , senior staff research engineer at Tenable . “Some surveys put AI usage among security professionals generally at 90%, so it’s unsurprising that this volume of patches may be the norm,” Narang said. “Pandora’s proverbial box has been opened, and as more advanced AI models become available, we expect the norm to continue upward across the board, not just for Patch Tuesday.” June’s zero-day bugs include CVE-2026-49160 , a denial of service vulnerability affecting a range of web servers, including Microsoft Internet Information Services (IIS). Microsoft says the flaw was reported by OpenAI’s Codex. Two of the zero-days addressed this month appear to stem from recent vulnerability disclosures by Nightmare Eclipse , the nickname chosen by a security researcher who has been dropping exploits for various Windows flaws. One of those, dubbed “GreenPlasma,” leverages an elevation of privilege weakness in the Windows Collaborati
[https://www.youtube.com/watch?v=3WqOP2iL6R0](https://www.youtube.com/watch?v=3WqOP2iL6R0) The FBI is announcing Operation Riptide, an ongoing, coordinated law enforcement campaign targeting criminal actors and the key services they rely on, their infrastructure, their tools and services, their communications platforms, and their money.
ServiceNow is warning about a security incident after attackers exploited an unauthenticated access flaw through a vulnerable API endpoint, allowing them to query data from customer instances. [...]
Phishing simulation on an OpenClaw email agent with various configuration profiles showed that it was susceptible to tactics commonly used to compromise human users. [...]
SAP has released fixes for 15 vulnerabilities as part of its June 2026 Security Patch package, including four critical-severity flaws affecting SAP NetWeaver and SAP Commerce Cloud. [...]
Writing my own virtualized loader is something I’ve been wanting to do since I first read Microsoft’s deep dive on FinFisher’s multi-layered VM obfuscation back in 2018. FinFisher didn’t just use one layer of protection, it implemented a custom virtual machine with 32 opcode handlers, wrapped that in spaghetti code and anti-debug checks, and then buried a second VM inside the 64-bit payload. Microsoft’s researchers had to write their own IDA plugins and build a full opcode interpreter just to understand what the malware was doing. The idea that you could interpose an entire bytecode interpreter between your real logic and an analyst’s tools, making both static and dynamic analysis incredibly difficult, stuck with me. I made real progress toward this over
AI is changing the economics of offensive security. Models can now accelerate vulnerability discovery, reason about attack paths, draft exploit logic, and speed up remediation guidance. For defenders, that is a meaningful step forward. It is also the hard part. The capabilities that help defenders move faster also help attackers because cyber AI is dual-use […] The post Trusted Access, Human Validation, and the Future of AI Pentesting appeared first on Synack .
Overview Microsoft-signed UEFI bootloaders of the open-source shim project, primarily from version 0.9 and earlier, were identified as vulnerable to Secure Boot bypass. To mitigate this risk, the affected bootloaders will be added to the Microsoft UEFI Forbidden Signature Database (DBX). Once the DBX update is applied, these bootloaders will no longer be trusted for execution during the boot process. An attacker could exploit these vulnerable shim bootloaders using a Bring Your Own Vulnerable Driver (BYOVD)-style technique to execute arbitrary code during the early boot phase, prior to operating system initialization, thereby bypassing Secure Boot protections. Description The Unified Extensible Firmware Interface (UEFI) standard defines the modern firmware architecture used to initialize hardware and transfer control to the operating system during system startup. On systems with Secure Boot enabled, UEFI applications and drivers must be cryptographically signed and verified before execution. Trust for these signatures is established through several firmware-managed databases, including the authorized signature database (DB), which commonly contains the "Microsoft Corporation UEFI CA 2011" certificate. This Microsoft certificate is widely used to sign third-party boot components intended to run under Secure Boot. The open-source UEFI shim project is a small, signed bootloader that Microsoft signed using the "Microsoft Corporation UEFI CA 2011" certificate. Shim acts as a bridge between the motherboard's UEFI firmware and the operating system (typically a Linux distribution). Its purpose is to allow Linux distributions to boot with Secure Boot enabled without requiring every individual distribution's key to be built into the motherboard's NVRAM settings. In doing so, shim allows Linux distributions and other third parties to esta
What are your recommendations for platforms to post IOCs on?
Meta on Tuesday announced that it will use information shared by other businesses to personalize users' feed and responses from its artificial intelligence (AI) chatbot, expanding its scope beyond targeted ads. "Businesses often share information about people's activity on their sites with us to make ads more relevant," Meta said in a statement. "We already use this data - like games you play
Anthropic is releasing Claude Mythos 5 to trusted organizations and Claude Fable 5 to the public, a version it says can’t be used for cyberattacks.
Veeam has released security patches to address a critical flaw in its Backup & Replication software that could result in remote code execution. Tracked as CVE-2026-44963, the vulnerability carries a CVSS score of 9.4 out of a maximum of 10.0. "A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user," Veeam said in a Tuesday advisory. It
Tech company says it ‘caught and disrupted’ NSO Group’s attempts to access accounts in Jordan and Lebanon A spyware firm has been targeting WhatsApp users with malicious links in contravention of a US court order forbidding it from doing so, Meta has said. In a post, Meta said WhatsApp had “caught and disrupted spear phishing attempts” by NSO Group, which a spokesperson said targeted a handful of users in Jordan and Lebanon. It had also caught the group creating “test accounts and groups” on WhatsApp. Continue reading...
University of Toronto researchers have built and tested a proof-of-concept AI-driven computer worm that uses a locally hosted open-weight large language model to reason its way through a network, generate tailored attack strategies for each target it encounters, and replicate itself, all without human intervention and without touching a commercial AI service. The preprint, posted to arXiv on
Google has released security updates to address 74 vulnerabilities, including one that has come under active exploitation in the wild. The high-severity vulnerability, tracked as CVE-2026-11645 (CVSS score: 8.8), has been described as an out-of-bounds memory access in V8, Chrome's JavaScript and WebAssembly engine. "Out-of-bounds read and write in V8 in Google Chrome prior to 149.0.7827.103
Organizations have more visibility than ever. Growing tech stacks provide greater coverage, and network security teams are increasingly adopting AI and automation to help with routine tasks and reduce manual effort. But the same challenges persist. Outages still last hours, causing significant financial losses, operational disruption, and reputational impact. Threat response and mean time to
Worm is a desktop forensic acquisition tool for authorized investigations. It brings disk imaging, memory acquisition, Android collection, hash verification, case output handling, image viewing, and reporting into one native application. The app runs as a real desktop window on Linux and Windows. [https://github.com/noirlang/worm](https://github.com/noirlang/worm) [https://worm.noirlang.tr/](https://worm.noirlang.tr/)
I scanned Chrome extension manifests for **chrome\_settings\_overrides** and found 23 extensions silently routing 758,000 users' searches through hidden monetization networks. The pattern: install a free extension (satellite imagery, maps, news reader), your default search gets quietly replaced and every query goes through the operator's middleware before reaching a search network, generating affiliate revenue you never consented to. Key findings: * 8 distinct brokers behind these extensions. If one extension gets pulled, another goes up under a different name. * Several extensions have zero functionality beyond the search override * One extension affirmatively claims "We don't track your searches" while its own privacy policy says otherwise * One uses runtime **declarativeNetRequest** injection so the real behavior is invisible to static analysis The \`hspart\` parameter in the final search redirect URL is the clustering key. One value maps an entire broker network regardless of extension name, domain, or publisher identity. Full report: [https://malext.io/reports/SearchJack/](https://malext.io/reports/SearchJack/)
A malicious website can work out which sites you visit and which apps you open, using nothing but JavaScript and the timing of your SSD. The attack, called FROST, needs no native code, no extension, and no permission prompt. You open the page, leave the tab sitting there, and it watches the drive for contention in the background. Researchers at Graz University of Technology built it and
The Miasma supply chain campaign has sparked a fresh attack wave called Hades, this time involving 37 malicious wheel artifacts across 19 packages in the Python Package Index (PyPI) registry, as the Mini Shai-Hulud-style attacks continue to be refined and splintered to target specific ecosystems. "The compromised releases shipped a *-setup.pth file that attempts to execute automatically
Microsoft Entra Agent ID introduces dedicated identity concepts for AI agents in Entra ID. While agent identities are based on the existing service principal infrastructure, they add agent-specific objects and relationships such as agent blueprints, blueprint principals, agent identities, agent users, and dedicated authentication flows. From a security perspective, the important question is not only whether such agents exist in a tenant. It is also important to understand how agent identities differ from traditional service principals, such as enterprise applications. This includes identifying who controls them, how they authenticate, and what they can access. Introduction This post does not aim to provide a complete technical introduction to every Entra Agent ID object or authentication flow. These concepts are only summarized briefly to provide enough context for the security-relevant observations in the following sections. New Agent ID Objects With Entra Agent ID, Microsoft introduced several new objects and relationships for representing AI agents in Entra ID. These objects differ from the traditional App Registration and Enterprise Application model. In the traditional model, the relationship is usually relatively simple: an app registration defines the application, and an enterprise application represents the tenant-specific service principal. With Entra Agent ID, this model becomes more layered. Depending on the scenario, the relevant objects may include an agent blueprint, a blueprint principal, one or more agent identities, and optionally agent users.
Monday, June 8
Fake Interview deploys stealthy cross platform (macOS/Windows) through npm package install in take home assessment
NPM supply chain hidden as main payload in a take home project for a fake job interview..
The code WIRED identified is gone from the latest version of Meta AI, the companion app for the company’s smart glasses. Meta won’t say why or whether it’s coming back.
COPENHAGEN, Denmark, June 8, 2026 – Heimdal has achieved ISAE 3000 SOC 2 Type II certification for the sixth consecutive year, reflecting the company’s continued focus on operational security, accountability, and data protection. The 2026 audit covered the period from 1 April 2025 to 31 March 2026 and examined Heimdal’s controls across access management, data […] The post Heimdal® Marks Six Years of Consecutive ISAE 3000 SOC 2 Type II Certification appeared first on Heimdal Security Blog .
To reduce the amount of noise from questions, we have disabled self-posts in favor of a unified questions thread every week. Feel free to ask any question about reverse engineering here. If your question is about how to use a specific tool, or is specific to some particular target, you will have better luck on the [Reverse Engineering StackExchange](http://reverseengineering.stackexchange.com/). See also /r/AskReverseEngineering.
A WIRED timeline shows how dozens of governments, companies, and other organizations across Europe are moving, or planning to shift, away from US Big Tech.
Sunday, June 7
Slapping an LLM onto a security tool without guardrails is a massive liability. In digital forensics and incident response (DFIR), an AI hallucination can ruin an entire chain of custody. An answer without mathematical, binary proof is completely worthless. If an AI agent cannot anchor its reasoning to exact offsets, hashes, and unmanipulated timestamps, it has no business touching forensic data. With **Crow-Eye v0.11.0**, we are pushing a massive update to our full-spectrum forensic lifecycle platform. This release introduces a hardened AI compliance architecture and completely upgrades the core correlation engines. We are treating the underlying intelligence layer like a highly supervised junior analyst. Everything it sees is hashed, everything it thinks is visible, its memory management is strictly audited, and its ability to alter rules is completely sandboxed. Here is exactly how we are enforcing forensic integrity under the hood in v0.11.0: # 1. AI Compliance & Governance # Evidence Seal & Cryptographic Chain of Custody Every single time the AI interacts with your forensic data, it is cryptographically verified. * **The Process:** Before any payload is passed to the AI model, the `evidence_seal.py` service steps in. * **Hashing & Provenance:** It calculates the SHA-256 hash of the exact bytes being sent and attaches metadata tracking the absolute source (e.g., `database:table:rowid`), token count, and the specific AI model used. * **Hash-Chaining:** This metadata is written to an append-only JSONL ledger. Each new record incorporates the hash of the previous record. If a single byte of historical evidence is tampered with, the entire cryptographic chain breaks instantly. # The TruncationAuditor Service (Context Auditing) AI context windows are a massive compliance bottleneck. Silent truncation—where a tool quietly drops data when limits are exceeded—is unacceptable in an investigation. The `TruncationAuditor` service acts as a strict forensic bookkeeper to log exactly how history is modified during our Self-Healing Context routine. * **The Append-Only Audit Log:** Events are permanently written to `<case>/EYE_Logs/truncation_audit.log`, tracking whether data was compressed (`SUMMARIZED`) or entirely removed (`TRUNCATED`). * **High-Fidelity Tracking:** Every single dropped or compressed message records its unique Message ID, token count, reason (e.g., `budget_exceeded`), extra JSON metadata, and a SHA-256 Content Hash of the exact message text to mathematically prove what was removed. * **Tamper-Evident Hash-Chaining:** Each log entry combines its content with the hash of the previous log line using a `chain=...` signature. If a rogue actor manually deletes a record from the text log to hide missed evidence, the chain breaks instantly, and the `verify_chain()` check fails. * **Protocol Compliance Panel:** The auditor exports this ledger into a structured JSON array (`audit_trail.json`). The React UI reads this to give investigators a clean visual timeline of exactly what was preserved, summarized, or dropped. https://preview.redd.it/7yysi31xgu5h1.png?width=3394&format=png&auto=webp&s=16032abda1bbbccd2986be1479e37a0c45ec5a69 # The ThinkingStep Protocol (Anti-Black-Box Streaming) The AI is hard-coded to "show its work." The `ThinkingStep` protocol bridges the Python backend (`eye_bridge.py` and `query_processor.py`) and the React frontend (`EyeDialogue.tsx`), streaming real-time updates over `QWebChannel` across 4 distinct, auditable phases: * **Phase 1: thinking (Intent Detection):** The backend queries the LLM to determine intent (e.g., separating general questions from direct MFT queries). The UI displays "Analyzing request..." * **Phase 2: rag (Retrieval-Augmented Generation):** The backend searches local forensic rules inside `configs/knowledge_base/` (like pulling up Living off the Land tactics for PowerShell analysis) and shows you exactly what was fetched. * **Phase 3: tool\_call (Execution):** If the AI needs hard data, it sends a structured command to the backend to fire off a tool (e.g., executing a raw SQLite database query). The UI displays a dedicated "Tool Execution" block exposing the exact arguments, execution status, and raw JSON payloads returned. This layer loops sequentially if multiple tools are required. If a tool fails on a bad SQL query, the step turns red, exposes the raw Python exception, and allows the AI to catch the error in its context to heal and try a corrected query. * **Phase 4: synthesis (Final Generation):** The backend bundles the RAG knowledge and tool results securely using the Evidence Seal, routing them to the model to stream out the final human-readable response. * **UI Transparency:** In the frontend, these phases are rendered as interactive, collapsible accordion blocks. You can expand a tool block to verify every database query syntax or piece of documentation the AI used before arriving at its final conclusion. # Governance Enforcement Protocols (GEP Rules 9-11) When the AI acts as an author (like generating correlation rules), it is locked down: * **Reasoning Required (R9):** The AI cannot create or edit any rule without rendering a clear text justification. * **Evidence Linking (R10):** The AI cannot hallucinate a rule. It must bind it back to the exact physical forensic artifact (`related_evidence`) that prompted it. * **Read-Only Built-ins (R11):** The AI is strictly sandboxed from modifying human-authored rules or built-in system defaults. # 2. Core Engine Upgrades With the AI heavily supervised, v0.11.0 also delivers massive architectural upgrades to the data engines feeding the platform. **Advanced Core Correlation Engine Upgrade** An adversary leaves footprints across multiple layers of the system simultaneously. * **Deep Artifact Stitching:** Crow-Eye automatically maps the connective tissue between Master File Table (MFT) records, Registry hives, LNK files, and Jump Lists. * **Instant Timeline Reconstruction:** The engine identifies non-obvious relationships instantly, allowing you to trace an execution lifecycle from initial file access straight to system persistence without manual cross-referencing. **Ironclad Identity Engine Upgrade** Attributing actions to specific security identifiers (SIDs) in modern Windows 11 environments can get incredibly messy during high-stress triage. * The upgraded **Identity Engine** brings precise, deterministic execution-context tracking. It resolves user sessions, elevation states, and mapped SIDs with absolute certainty, eliminating ambiguity during credential abuse investigations. For the next release, I am focusing completely on user bugs and performance edge-cases. Please feel free to contact me for any bug reports or support queries you can find all of my direct contact details on the official website:https://crow-eye.com/ **GitHub:**[https://github.com/Ghassan-elsman/Crow-Eye](https://github.com/Ghassan-elsman/Crow-Eye) for the full details of the Resale notes please check [https://github.com/Ghassan-elsman/Crow-Eye/releases/tag/0.11.0](https://github.com/Ghassan-elsman/Crow-Eye/releases/tag/0.11.0) Good hunting,
EDRChoker uses **Policy-based Quality of Service (QoS)** to set hard bandwidth caps (throttling) on Endpoint Detection and Response (EDR) agents, causing them to always time out - effectively blocking them.
I recently learned about multiple sandbox bypasses discovered in Twig by project Glasswing. From the descriptions, only CVE-2026-46640 and CVE-2026-46633 seemed universally exploitable, so I decoded to research them. This writeup documents my development of payloads for the CVE-2026-46640 and the corresponding SSTImap module.
Saturday, June 6
Plus: Hackers use Meta’s AI bots to hack Instagram accounts, Anthropic helps NSA hackers, a decades-long GPS satellite mystery may have been solved, and more.
Friday, June 5
At Gartner SRM 2026 this week I gave a talk called “Cutting Through AI Noise: Defending Against Machine-Speed Cyber Adversaries.” The room was full of security leaders who’ve been through enough hype cycles to be skeptical of seeing AI on the label. That skepticism is warranted, and I built the session around it. Here’s what […] The post What I Told Security Leaders at Gartner SRM 2026 appeared first on Synack .
Thursday, June 4
Adversaries have always relied on legitimate tools to carry out their attacks. These tools are already trusted by security solutions, which allows them to blend in with normal activity, maintain a low footprint, and make detection much harder for defenders. By using these legitimate tools, adversaries can carry out a wide range of a
In our last post we used a Claude skill to systematically beat down VirusTotal detection rates on offensive security tools, with a brief mention of a new loader we’d been using to apply those techniques in bulk. This post is about that loader, which we call WasmForge. WasmForge is, from the user’s perspective, a build wrapper. You point it at a Go project and you get back a Windows or macOS binary that runs your tool but doesn’t look anything like it. Internally it’s a lot more. It’s a Go-to-WebAssembly compiler, a custom Wazero fork, around eighty host shim functions for MacOS and Windows APIs, and a healthy amount of evasion techniques from our previously discussed skill. The whole pipeline exists to solve one specific problem: take an existing offensive security tool, change zero lines of its source code, and produce a binary you can actually drop on a hardened endpoint. The Tool Authors Won, Then The Tool Authors Lost Many red team engagements can be completed using the same handful of established tools. Sliver for
One thing that kept slowing me down during investigations and security assessments wasn't exploitation. Once I had initial access (e.g. Domain Admin), there is often still a large gap in demonstrating the exploitability of business-critical assets. You might tell a customer, "I got Domain Admin, job done". But in reality, that’s not always enough. A CISO may understand why it’s critical, but what would the CTO or CEO say? They need dead-head proofs, so you go beyond and look for business-critical assets, that\`s where post-exploitation begins!) My small research is about logs. Windows ones. Collecting Windows Event Logs does not simply mean copying EVTX files. We\`ve got some problems here :) \- How do I acquire logs when Windows blocks direct access? \- How do I exfiltrate the content? \- How do I process it? \- How do I work around AV, even trying to read it? \- How do I get even some use out of it? In practice, things become more complicated when investigating live systems. Windows keeps many log files open and actively written to. After several iterations I ended up building a small open-source project called LogHound. I'm curious how other people here approach large-scale log analysis during: * DFIR investigations * Red Team operations * malware analysis * incident response * system troubleshooting So here is how i solved all the problems: **How do I acquire logs when Windows blocks direct access?** We know - Windows blocks every .evtx file with process and does not let anyone to read\\copy\\download it. So we\`re looking for a simple solution As it is a post-exploitation engagement, we could make use of native Windows tools, especially - wevtutils. A small command lets us do all the dumping/filtering job `wevtutil epl Security "%s" /q:%s` **How do I exfiltrate the content?** As we are talking about Red Team engagements, we would like to make use of smth legitimate and widespread everywhere - and impackets smb library fits the best here. Minimum load logs, straightforward protocol and speed. **How do I process it?** If I were in a defender role, I would probably use some PowerShell module or GUI. Here we do not have such privileges, so Python\`s evtx lib + multithreading + filtering at start help to do the job quickly. **How do I work around AV, even trying to read it?** Well, nowadays you cannot just log in to Windows, get some shell and execute commands. 99% of available pentester tools would be blocked by every EDR, so we are also looking for smth legit and widespread. Most reason that is not the case with GitHub tools - EDRs collects behavioral patterns even with legit protocols and detects it easy. I\`ll use a legit WMI query with Win32\_Process.Create, hoping I won't leave a lot of indicators... and, for now, it works! **How do I get even some use out of it?** Collecting post-exploitation data is a fun process, but you can't really make a profit from gigabytes of raw data, and I\`m glad there are strong visualisation frameworks like BloodHound. It has a pretty convenient JSON scheme and, if not very adaptive but usable API. So I decided - importing that data to the BloodHound scheme would work out the best. And after all, we could continue our post-exploitation activities with a bit more useful information :) Project: [LogHound GitHub Repository](https://github.com/RNB-Team/LogHound)
At Accenture’s scale, training alone cannot solve every security problem. That was the reality facing Kris Burkhardt, Global CISO at Accenture. With a workforce of more than 800,000 people, close to 80,000 new hires each year, and a sprawling global attack surface, traditional penetration testing was no longer enough. A once-a-year compliance audit may check […] The post How Accenture Turned Penetration Testing Into a Force Multiplier for Security appeared first on Synack .
Learn four practical ways GreyNoise improves SOC outcomes—from reducing alert volume and surfacing targeted threats to identifying compromised hosts.