Blahalla

Russia-Linked ‘GreyVibe’ Attackers Use AI to Supercharge Cyberattacks

www.securityweek.com · 4 months ago

Researchers warn GreyVibe’s extensive use of ChatGPT, Gemini, and other AI tools offers a glimpse into how future cybercriminal and state-aligned groups will operate.
Hackers exploit FortiClient EMS flaw to push infostealer malware

www.bleepingcomputer.com · 4 months ago

Hackers are exploiting an authentication bypass vulnerability (CVE-2026-35616) in FortiClient Enterprise Management Server (EMS) to deliver an undocumented credential stealer called EKZ.
Critical Gogs RCE Vulnerability Lets Any Authenticated User Execute Arbitrary Code

thehackernews.com · 4 months ago

A critical security vulnerability has been disclosed in Gogs, a popular open-source self-hosted Git service, that allows an authenticated user to execute arbitrary code under certain conditions. The security flaw, per Rapid7, is rated 9.4 on the CVSS scoring system. It does not have a CVE identifier. "The vulnerability allows any authenticated user to achieve remote code execution (RCE) on
Geordie Raises $30 Million for AI Security and Governance Platform

www.securityweek.com · 4 months ago

The funding round was led by Balderton Capital, with additional support from Crosspoint Capital and previous investors General Catalyst and Ten Eleven Ventures.
Threat Intel: Kemper Corporation Hit by ShinyHunters Salesforce Extortion Campaign (269k Accounts Ingested by HIBP)

www.technadu.com · 4 months ago

Kemper Corporation reportedly exposed approximately 270,000 accounts following an alleged breach by ShinyHunter. The compromise involved sensitive account details belonging to the company. Security experts recommend users change passwords and monitor for unauthorized activity immediately. No CVEs were mentioned regarding this incident.
FBI Warns Companies About Ransom Gang’s Fake IT Support Tactics

www.techrepublic.com · 4 months ago

The FBI warns Silent Ransom Group is targeting US law firms with phishing, fake IT calls, and in-person visits to steal data for extortion.
A.I. Is Making Scams Hard to Spot. Here’s How to Protect Yourself.

www.nytimes.com · 4 months ago

A criminal could be masquerading as a celebrity, web store or family member asking for your money. Detecting scams requires a new approach.
Apple May Bring Android-Style Theft Detection to iPhones

www.techrepublic.com · 4 months ago

Apple is reportedly testing an iPhone anti-snatching feature that would lock stolen devices using motion signals and checks for familiar locations.
Agentic AI Isn't Risky; the Way Orgs Deploy It Is

www.darkreading.com · 4 months ago

AI agents aren't black boxes, they're models interacting with software tools. The risk lies in their overlap.
Threat Actors Exploit Critical FortiClient EMS Flaw to Deploy Credential Stealer

thehackernews.com · 4 months ago

Threat actors are continuing to exploit a critical, now-patched security flaw impacting FortiClient Endpoint Management Server (EMS) deployments to deliver credential-stealing malware. "The campaign abused trusted endpoint management infrastructure to deliver malware across managed endpoints," Arctic Wolf said. "Threat actors disguised the credential stealer payload as a Fortinet endpoint
Google’s $135M Android Privacy Settlement: Who May Be Eligible

www.techrepublic.com · 4 months ago

Google’s $135 million Android settlement could pay eligible US users who used Android devices with cellular data since November 2017.
The Gentlemen ransomware: Dissecting a self-propagating Go encryptor

www.microsoft.com · 4 months ago

Microsoft Threat Intelligence presents a comprehensive analysis of The Gentlemen, a Go-based ransomware deployed by affiliates of Storm-2697 that combines per-file ephemeral key encryption with an aggressive self-propagation module to deploy itself across an entire network using series of simultaneous lateral movement techniques per target.
Drupal PostgreSQL SQL Injection: From SELECT-Only to RCE

blog.lexfo.fr · 4 months ago

A critical vulnerability chain has been identified in Drupal related to its interaction with PostgreSQL. Attackers can leverage SQL injection techniques to achieve full Remote Code Execution. Proper input sanitization and strict query validation are essential measures to prevent exploitation. Administrators must promptly apply available patches to mitigate this serious security risk.
Carnival Data Breach Exposed 6 Million People

www.securityweek.com · 4 months ago

Data breach leaves nearly 6 million Carnival customers navigating identity theft risks.
New Gogs zero-day flaw lets hackers get remote code execution

www.bleepingcomputer.com · 4 months ago

An unpatched zero-day vulnerability in the Gogs self-hosted Git service can allow attackers to gain remote code execution (RCE) on Internet-facing instances.
How SIEM helps MSPs reduce noise and stop threats faster

www.bleepingcomputer.com · 4 months ago

MSPs don't lack security data. They struggle to separate real threats from alert noise. Kaseya explains how SIEM helps MSPs improve visibility, reduce fatigue, and respond faster.
Microsoft Slams Public Zero-Day Disclosures Amid GitHub Researcher Account Removal

thehackernews.com · 4 months ago

Microsoft has come out strongly in favor of Coordinated Vulnerability Disclosure (CVD), urging the research community to share their findings and give affected vendors an opportunity to better understand the impact and address them before they are publicly disclosed. The development comes after a researcher named Chaotic Eclipse (aka Nightmare-Eclipse) disclosed details of multiple zero-day
MyPillow listed on ransomware gang’s leak site, but denies it has been breached

www.bitdefender.com · 4 months ago

A notorious ransomware gang claims to have stolen MyPillow's private data, but CEO Mike Lindell calls it a politically motivated "hit job." With the countdown ticking toward a massive dark web leak, who is telling the truth? Read more in my article on the Hot for Security blog.
Hackers Pivot from marimo RCE to Internal Database Using LLM Agent

gbhackers.com · 4 months ago

A newly observed intrusion demonstrates how attackers are replacing static playbooks with AI-driven agents that adapt in real time. The attack began on May 10, 2026, როდესაც threat actors exploited CVE-2026-39987, a remote code execution flaw in the marimo notebook environment. Once inside, the attacker harvested cloud credentials from environment files and system paths. Unlike
ThreatsDay Bulletin: Claude Security Plugin, Azure Priv-Esc, Kali365 MFA Bypass, FIFA Scams +15 More

thehackernews.com · 4 months ago

Every time you think the industry has finally stopped doing some reckless, low-effort crap, somebody spins up a fresh box full of sketchy loaders, fake installers, recycled social-engineering bait, and enough exposed infrastructure to make you wonder if prod is just a public beta now - meanwhile some researcher casually drops a technique that turns a "minor" foothold into total account
New BTMOB Android Malware Enables Full Device Takeover

www.securityweek.com · 4 months ago

Delivered via phishing lures, the malware combines financial theft with data exfiltration and remote access.
8 Best Enterprise Password Managers (2026)

www.techrepublic.com · 4 months ago

After reviewing the top enterprise password managers in the market, I found Keeper to be the best overall, particularly for its ease of use, and management-focused feature set.
Indian CERT urges firms to contain exploited internet-facing flaws within 12 hours

www.csoonline.com · 4 months ago

India’s cybersecurity agency, CERT-In, has urged organizations to patch, mitigate, or isolate known exploited vulnerabilities affecting internet-facing “crown jewel” systems within 12 hours where feasible, warning that AI-assisted attacks are dramatically compressing the time between vulnerability disclosure and exploitation. The recommendation, part of a sweeping new CERT-In blueprint on defending against AI-assisted cyber exploitation, signals a significant escalation in expectations around enterprise vulnerability management, exposure reduction, and operational resilience. The 38-page framework also recommends one-day remediation for critical externally exposed vulnerabilities, three days for critical internal vulnerabilities affecting high-value systems, and five days for high-severity flaws based on risk prioritization. CERT-In said threat actors are increasingly using AI to accelerate reconnaissance, vulnerability discovery, phishing, malware generation, and automated exploitation workflows. “Exploitation timelines are reducing significantly,” the agency warned in the advisory, adding that attacks are expected to become “increasingly autonomous.” An operationally disruptive target Security analysts said the headline 12-hour expectation is likely to force enterprises to rethink traditional weekly or monthly patching cycles, but cautioned that the guidance is more nuanced than a blanket patch mandate. “The 12-hour window is the outlier, realistic only as a containment target on a narrow set of exposed assets, never as a patch-completion target across sprawling estates burdened by fragmented infrastructure, layered approvals, outsourced operations, and legacy dependency,” said Sanchit Vir Gogia, chief analyst at Greyhound Research. Gogia said the blueprint’s tiered approach is more significant than the headline remediation clock itself because it ties response timelines to exposure and operational criticality rather than applying a uniform patching mandate across all systems. “The five-day high-severity window is comfortable for most enterprises. The three-day critical-internal window is where the pressure actually bites,” he said, particularly in sectors such as finance, telecom, healthcare, and operational technology environments where uptime concerns complicate rapid change management. Apeksha Kaushik, senior principal analyst at Gartner, said the biggest challenge for many organizations will not necessarily be deploying patches, but achieving the operational maturity needed for rapid exposure management. “The primary barriers are not just technical, but operational. Most organizations lack real-time asset visibility, automated vulnerability prioritization, and cross-functional incident response playbooks,” Kaushik said. “The most acute struggles will be in asset discovery, risk-based prioritization, and orchestrating rapid response across silos,” she added. From vulnerability management to exposure management The blueprint repeatedly emphasizes that traditional periodic security assessments are becoming insufficient against AI-enabled attacks capable of rapidly weaponizing newly disclosed flaws. Instead, CERT-In is pushing organizations toward continuous exposure management, threat-informed defense, continuous monitoring, and adversarial testing. Notably, the framework leans heavily on temporary mitigations, including isolation, access restrictions, WAF/API protections, enhanced monitoring, and compensating controls when immediate patching is not possible. Analysts said that approach makes the timelines more achievable operationally, but also shifts the burden onto asset visibility and exposure intelligence. “Compensating controls do make the timelines more workable. They also remove every excuse,” Gogia said. “If you cannot isolate, restrict, or monitor quickly, the problem was never patch cadence. The problem is that you do not know your own exposure.” Kaushik similarly said the guidance effectively pushes organizations toward more mature exposure management capabilities. “Organizations must be able to rapidly identify affected assets, assess risk, and deploy effective interim controls,” she said, adding that enterprises lacking mature asset inventories, segmentation, and monitoring capabilities will struggle to operationalize the guidance at scale. The blueprint also calls for continuous vulnerability assessments, AI-assisted security testing, adversarial simulations, penetration testing, and red teaming exercises. A preview of future global standards? Analysts said CERT-In’s remediation expectations are among the most aggressive currently issued by a national cyber agency and may influence broader international vulnerability-management practices as AI compresses attacker timelines globally. “CERT-In has done something the West has largely avoided: it has set standing clocks by asset category rather than deadlines by individual vulnerability,” Gogia said. He contrasted the framework with CISA’s Known Exploited Vulnerabilities (KEV) program, which typically uses vulnerability-specific remediation deadlines rather than persistent enterprise-wide remediation clocks. “The fixed-clock model looks aggressive today because the rest of the world has not caught up, not because it is reading the threat wrongly,” Gogia said. Kaushik said the framework could create operational challenges for multinationals whose global service-level agreements are less stringent than India’s expectations. “For providers, this may create a compliance gap where internal SLAs are less stringent than India’s requirements, necessitating a reassessment of global patching and mitigation processes,” she said.
Critical FortiClient EMS Vulnerability Exploited in Fresh Attacks

www.securityweek.com · 4 months ago

Fortinet rolled out hotfixes for the security defect in April, warning that it had been exploited in the wild as a zero-day and urging immediate patching.
Romanian gets 5 years in prison for hacking Oregon govt network

www.bleepingcomputer.com · 4 months ago

A Romanian national was sentenced this week to 56 months in federal prison for breaking into an Oregon state government computer network and fr cyberattacks targeting dozens of other U.S. victims.
IBM and Red Hat Commit $5 Billion to Secure Open Source Supply Chains Under “Project Lightwell”

www.securityweek.com · 4 months ago

Project Lightwell is designed to fix vulnerabilities without breaking what is already in production.
Focus on Cyber Insurance: How Quantifying Risk Is Reshaping Security

www.darkreading.com · 4 months ago

In this latest installment of the Reporters' Notebook video series, we discuss how cyber insurance is forcing organizations to quantify risk, what's covered (and what's not), and why this could be the best thing to happen to cybersecurity.
GlassWorm falls, but the repo problem is far from solved

www.csoonline.com · 4 months ago

Taking down a sprawling malware operation once signaled progress in securing the open-source ecosystem. Now, it barely registers. The GlassWorm campaign disruption comes at a moment when attackers can quickly reconstitute, and defenders are increasingly grappling with a new challenge: distinguishing real threats from automated noise. “I think coordinated actions, like GlassWorm, can sever control, significantly increase attacker costs, buy time for remediation, and signal the possibility of a fightback,” said Agnidipta Sarkar, chief evangelist at ColorTokens. “But most takedowns are temporary actions in a long fight.” The CrowdStrike-led takedown, conducted alongside Google and the Shadowserver Foundation, disrupted infrastructure linked to the campaign that had poisoned hundreds of repositories with malicious packages targeting developers. A day after the takedown, in an independent development, the OSV database withdrew 157 malware reports after maintainers determined the submissions were likely automated false positives. Takedowns help, but analysts question long-term impact The takedown happened on May 26, at 14:00 UTC, with CrowdStrike confirming the operation to have struck down “all four of GlassWorm’s command-and-control (C2) channels simultaneously”. This reportedly helped sever the botnet operators from their infected machines, blocking them from pushing out new malware. CrowdStrike described the GlassWorm operation as targeting infrastructure used to distribute malware through developer-focused repositories, an increasingly popular attack vector as adversaries chase CI/CD access, developer credentials, and downstream enterprise environments. GlassWorm was a cross-platform operation affecting Windows, macOS, and Linux systems, with trojanized VSCode extensions and compromised npm and Python packages for information and credential harvesting. “As part of our disruption efforts, we are working with partners to bring more pain to attackers, especially when we see them abusing our products or targeting our users,” said Google Threat Intelligence Group’s (GTIG) chief analyst, John Hultquist, in an X post. Still, the broader economics of repository abuse remain unchanged. Open-source ecosystems continue to offer attackers low-cost distribution, massive reach, and relatively weak identity verification compared to traditional software distribution channels. That means operators behind campaigns like GlassWorm can often reappear quickly under new accounts, domains, or package names. “It is disruption, not eradication,” Sarkar warned. “To build resilience after a takedown, defenders should prioritize rapid post-takedown scanning to detect the reemergence of malicious artifacts across related repositories and distribution platforms. ” They should then establish granular micro-perimeters, build capabilities to contain propagation across workloads, endpoints, IT/OT/IoT/cloud assets, and limit the blast radius of supply-chain compromises (e.g., a poisoned npm package or a GitHub workflow stealing creds can’t easily pivot). Sarkar advised developers and organizations to establish “granular micro-perimeters,” build capabilities to contain propagation across workloads, and limit the blast radius of supply-chain compromises. AI False positives are becoming part of the supply chain problem If GlassWorm highlights the persistence of real malware campaigns, the OSV withdrawal incident exposed a parallel issue affecting the open-source software (OSS) supply chain. It is the growing reliability surrounding automated security reporting. The withdrawal of 157 malware reports believed to be AI-generated false positives matters, especially when it includes packages like FastAPI v0.136.3. FastAPI is a heavily adopted Python framework powering production APIs, AI services, and cloud-native applications across industries. Even a few days of false flagging can trigger costly deployment delays, CI/CD disruptions, and hours of development time in isolating legitimate software. “I would recommend that enterprises be concerned enough about signal-to-noise problems to consider remedial measures, as automation erodes trust in defensive tools,” Sarkar said. “Unless you have a highly microsegmented enterprise, noise wastes analyst time, slows velocity, and risks missing sophisticated attacks amid fatigue.” In 2026, with AI-assisted malware and reporting both accelerating and rising false positives in SAST/SCA tools, defensive automation is getting asymmetrically compounded by supply-chain volume, he noted. In a blog post, Socket called bad OSV records particularly dangerous as the popular database gets rapidly carried through dependency scanners, CI checks, registry controls, SBOM tools, dashboards, and internal policy systems. All hope is not lost, though, as newer tools promise lower reliance on AI for hunting dependency vulnerabilities. CVE Lite CLI, a light-weight, JavaScript and TypeScript dependency vulnerability scanner, is offering developers a way to know dependency risks while they are still writing code, much earlier than failing automated scanners in CI pipelines.
Webinar: Why network incidents take too long to resolve

www.bleepingcomputer.com · 4 months ago

Many organizations can detect network issues quickly, but investigations and coordination often slow incident resolution. This webinar explores how automation and AI-assisted workflows can help IT teams reduce delays and improve response times.
Malicious Websites Exploit SSD Timing Signals to Monitor Visitor Activity

gbhackers.com · 4 months ago

Malicious websites can now exploit subtle SSD timing signals in modern browsers to quietly track what users are doing on their devices, including which sites and apps they open, using a new side‑channel technique called FROST. Security researchers Hannesweissteiner have revealed that a single drive‑by visit to a booby‑trapped page is enough for an attacker
New Edamame Platform Aims to Catch AI Coding Agents Going Off the Rails

www.securityweek.com · 4 months ago

France-based startup Edamame says its runtime verification platform uses host telemetry and AI analysis to detect coding-agent “intent drift,” secret theft and supply-chain attacks in real time.
New AI Usage Report: Enterprise AI Risk Is Heavily Concentrated Among a Small Group of AI "Power users"

thehackernews.com · 4 months ago

State of AI Usage Report 2026 (full report here) by LayerX Security reveals the extent of the enterprise AI visibility gap and why most organizations still don't understand where their AI exposure is actually coming from. The research shows that enterprise AI risk is not distributed evenly across users or platforms. Instead, it is heavily concentrated among a small group of AI power users and a
Gitea Vulnerability Exposed 30,000 Deployments to Attacks

www.securityweek.com · 4 months ago

The security flaw allowed attackers to pull private container images, exposing source code, credentials, and infrastructure.
Raising the Cybersecurity Stakes: Ante up for the Agentic Era

www.securityweek.com · 4 months ago

CISOs are now facing machine-speed attacks and asking, “How do I agent?” The industry must provide remediation at scale.
Carnival Cruise confirms data breach affecting nearly 6 million people

www.bleepingcomputer.com · 4 months ago

Carnival Corporation, the world's largest cruise line operator, has confirmed a data breach affecting nearly 6 million people claimed by the ShinyHunters extortion gang in April 2026.
VaultJacking Attack Exposes Google Password Vaults via Single PIN

gbhackers.com · 4 months ago

A newly disclosed phishing technique dubbed “VaultJacking” is raising serious concerns across the cybersecurity community after researchers demonstrated how a single captured Google Password Manager (GPM) PIN can expose an entire user credential vault. The attack shows that even passkeys widely promoted as phishing-resistant can be indirectly compromised when attackers target the underlying sync infrastructure
Top 10 Best Mobile Application Security Testing (MAST) Tools in 2026

gbhackers.com · 4 months ago

As mobile usage continues to dominate the digital landscape, securing mobile applications has never been more critical. The year 2026 brings new challenges to the table: sophisticated AI-driven cyberattacks, complex vulnerabilities, and the rapid evolution of continuous integration workflows. For enterprises and developers, relying on outdated security measures is no longer a viable strategy; proactive
Gitea Container Registry Vulnerability Could Lead to Private Image Exposure

gbhackers.com · 4 months ago

A critical vulnerability, tracked as CVE-2026-27771, has been discovered in Gitea’s built-in container registry, allowing unauthenticated remote attackers to access private container images without credentials. This flaw poses a serious risk as it can expose sensitive application data, including source code, secrets, and infrastructure configurations. Due to its severity and ease of exploitation, security experts
AI-Generated npm Malware Leaks Hacker’s Private GitHub Token

gbhackers.com · 4 months ago

A newly discovered malicious npm package is drawing attention across the cybersecurity community after inadvertently exposing its own operator’s private GitHub token. Identified by OX Security researchers, the package, named mouse5212-super-formatter, operates as an infostealer that silently exfiltrates sensitive files from compromised systems while masquerading as a legitimate development utility. The package, which has already reached
The AI governance imperative you can’t afford to ignore

www.csoonline.com · 4 months ago

CIOs rushing to roll out AI agents without real visibility into their decision-making processes are flirting with disaster. According to AI experts, deploying agents without observability processes and tools creates a ticking time bomb with the potential for huge negative consequences. Many companies are deploying AI agents and expecting them to increase productivity with little human intervention, observes T.J. Marlin, CEO of AI security firm Guardrail Technologies. That’s the wrong approach, he says. Instead, IT teams need to keep a close eye on agents and adjust policies and practices throughout the agentic process. “It’s not just set it and forget it like a crock pot,” he says. “You don’t put it in the kitchen in the morning with the chicken inside and come back at night and have a great dinner. The organizations doing that are going to be on the front page because they just had some terrible thing happen to them.” Many organizations are rapidly deploying agents because of a fear of missing out, while not understanding the nuances of the technology, Marlin says. Some IT leaders seem to compare agents to robotic process automation, when RPA results are far more deterministic, he adds. “There’s a talent shortage and a knowledge shortage and people are building at pace without checking whether it’s correct and it’s operating as expected,” he says. “Those are all the hallmarks of the worst disasters that I’ve seen across my career.” A recent report from agent governance vendor TrueFoundry puts numbers behind fears of unregulated agents. A survey of more than 200 enterprise AI leaders found that 54% of organizations represented can’t fully trace what their agents are doing and 56% have no centralized agent control or governance layer. While TrueFoundry has an interest in driving agent governance forward, many other AI experts see the same problems. Governing blind Difficulties with governance and observability are major impediments to the deployment of productive agents, and many organizations are deploying agents without creating a centralized list of them, says Mahesh Kumar Goyal, senior data and AI expert at Google. “Most enterprises have no inventory of the agents already running in production, they’re trying to govern what they can’t see,” he says. In addition, traditional SIEM and EDR security tools were built to spot human anomalies, not rogue agents, he notes. “An agent running code perfectly 10,000 times in a row looks normal even if it’s been hijacked,” he says. Running fully autonomous agents is not a good idea, he adds, and organizations need to think about least-privilege scoped tool permissions, policy enforcement layers that mediate every prompt and tool call, and end-to-end tracing that stitches prompts, tool calls, and downstream actions into one auditable trail. “The financial system doesn’t run on trust; it runs on auditability, reconciliation, and circuit breakers,” Goyal says. “Agents will mature the same way. Tiered autonomy is the realistic answer: free rein on low-stakes tasks, human-in-the-loop on consequential ones.” Part of the problem is that agents have upended the models used to determine whether traditional software was running correctly, adds Adel El Hallak, vice president of AI software at Nvidia. With traditional software, QA and security professionals could look at the code to debug problems, but agents make decisions in the runtime environment of an AI model. The source of truth for agents resides in the traces, the records of the execution flow, not in the code, he adds. Collecting traces , in essence, detailed logs, is a start toward agent governance, but organizations need to be able to act on the information, he says. “For you to trust something, it has to be transparent, and observability is foundational to transparency,” El Hallak adds. “But just observing is not enough. We need to be able to take those signals and turn them into something actionable.” Agent governance goes beyond observability to allow organizations to test and fine-tune agents continuously, he says. The tools are out there, with companies like Nvidia building their own internal governance frameworks, and several other vendors offering agent observability and governance tools, he notes. “It’s not enough to just have the behavioral data, to capture the feedback data,” he says. “The system should allow me to annotate, change, augment, or create additional feedback data, and then I can use that data to improve my agent as a whole.” The governance bottleneck At the same time, many companies moving into agent governance have found it can be a huge bottleneck if done wrong, says Nirmal Ganesh, senior director of product management for agentic workflow automation at cloud storage vendor Box. “I don’t believe we are past the hard part yet in terms of deploying agents in the enterprise,” he says. “Most companies are not yet good at those, and far fewer of them have gotten good at running them at scale with agent governance and observability.” Ganesh sees several problems, including agents running without clear permission models. “If an agent can see more than a person or access more than a person’s permission on content or data, that’s an incident is waiting to happen,” he says. However, some early agent governance models don’t scale. Some IT teams have defaulted to a position of humans needing to approve every agent output because that’s the safest option, he says. “In reality, this is rebuilding manual process with more checkpoints or suggestion points,” Ganesh says. “At a high volume, governance is your bottleneck to scale and no longer your safely net.” Organizations need observability and governance processes in place that are both scalable and comprehensive, he adds. Agent ROI will come from strong guardrails, clear permission models, and clear human-in-the-loop involvement, he says. “Every mature automation needs ongoing observability, workflows change, policies change, decisions change, new use cases show up,” he says. “Human intervention is always needed for what changes over time, but we need less intervention for known paths and more focus on exception handling and governance fine-tuning.” Observing output is not enough Governance can’t just focus on agent output, adds Marcelo Lorenzetti, founder and CAIO at legal services AI vendor SavvyLex. “The biggest challenge is not simply whether an agent produces a good answer,” he says. “It is whether the organization can prove what the agent accessed, what instructions it followed, what tools it invoked, what decisions it made, where a human intervened, and whether it stayed within authorized boundaries.” Without a full level of runtime visibility, companies are left with screenshots, logs, and after-the-fact explanations that may not meet legal, compliance, or security requirements, he says. Agents should be continuously verified instead of fully trusted, he adds, with governance engineered into the agent architecture itself. Governance should include role-based access, policy-bound execution, human approval thresholds, source and tool provenance, immutable activity records, confidence scoring, exception handling, and clear escalation paths when an agent reaches the edge of its authority, he recommends. “Observability should not be limited to whether the model responded,” Lorenzetti says. “It should show the full decision path from input to action.” AI agents have shifted the governance model that’s needed, he adds. “The core problem is that many companies are moving from AI that answers questions to AI that takes actions, but their governance models are still built for passive tools, not autonomous workflows,” he says.
2026 World Cup: Discussing The World’s Biggest Game’s Attack Surface

unit42.paloaltonetworks.com · 4 months ago

The 2026 World Cup presents major cyber risks from ransomware groups, state-aligned actors, and other groups targeting critical infrastructure. Learn more here.
Google Unveils AI Threat Defense Platform to Fight AI-Powered Cyberattacks

www.securityweek.com · 4 months ago

New AI Threat Defense platform combines capabilities from Mandiant, Wiz and Gemini to help customers fight AI with AI.
Critical Notepad++ Flaw Could Enable Remote Code Execution Attacks

gbhackers.com · 4 months ago

Notepad++ has released version 8.9.6.1 to address multiple security vulnerabilities, including critical flaws that could allow arbitrary code execution under specific conditions. The update, published on May 26, 2026, patches three vulnerabilities tracked as CVE-2026-48770, CVE-2026-48778, and CVE-2026-48800. These issues affect versions up to 8.9.6 and highlight risks tied to improper handling of configuration files.
Sextortionist sentenced to 33 years for targeting 145 children

www.bleepingcomputer.com · 4 months ago

A Canadian man was sentenced to 33 years in prison after pleading guilty to targeting more than 145 children across the United States, some as young as 6 years old, in an eight-year-long sextortion scheme.
Online Scams Have Evolved in the A.I. Era. Here’s What to Do.

www.nytimes.com · 4 months ago

A criminal could be masquerading as a celebrity, web store or family member asking for your money. Detecting scams requires a new approach.
BTMOB RAT Spreads Across Brazil, LatAm via MaaS Model

www.darkreading.com · 4 months ago

An advanced remote access Trojan is propagating online. Notably, it's delivered via an operator licensing model and features a no-code malware-development interface.
ClearFake Abuses BSC Testnet Contracts for Resilient C2 Operations

gbhackers.com · 4 months ago

Threat actors behind the ClearFake campaign have adopted a novel and highly resilient command-and-control (C2) architecture by leveraging BNB Smart Chain (BSC) testnet smart contracts, creating an infrastructure that is effectively immune to traditional takedown efforts. Unlike conventional malware campaigns that depend on easily disruptable infrastructure such as hosting providers or registrars, this approach embeds
What the industrialization of exploitation means for defenders

www.csoonline.com · 4 months ago

For decades, cybersecurity was a battle of skill. Elite attackers versus elite defenders. The rules of engagement were understood, even if the playing field wasn’t level. If you hired better analysts and bought better tools, hopefully you hardened your systems well enough and built detection capabilities that wore out the adversary’s patience. That era is over, and most security programs haven’t fully processed what replaced it. Adversarial AI has industrialized exploitation. What once required a coordinated team of technically sophisticated threat actors to manage reconnaissance, weaponization, lateral movement and persistence can now be executed autonomously, at machine speed, against thousands of environments simultaneously. Threat actors no longer need deep technical expertise. They need compute, capital and access to AI tooling, all of which are commoditized. Think about what your team used to rely on. Attackers left clues that telegraphed their presence, patterns you could learn, signatures you could catch and their campaigns moved slowly enough to track. That’s gone. Reconnaissance that took days now takes minutes. The attacks your tools were trained to recognize are being rewritten on the fly. And the coordinated human teams that once limited how many targets an adversary could hit at once? They can now be easily outmaneuvered by a single actor with the right AI tooling. Your architecture was designed for a threat that no longer exists. The problem is structural The gaps AI-enabled adversaries are exploiting aren’t primarily operational failures. They’re architectural ones. As enterprise environments expanded across cloud, OT, identity infrastructure and third-party integrations, security organizations responded by layering tools. Each new surface area got a new control, a new scanner, a new dashboard. This has created a security architecture that’s simultaneously complex and fragmented, generating enormous volumes of signal while producing limited clarity about where the actual risk lives. The specific failure modes are familiar to anyone who has worked through a real breach investigation. Controls that don’t share context mean a vulnerability scanner can flag a misconfiguration, an identity tool can flag an overprivileged account and an endpoint platform can generate an alert, none of them are able to answer the question an attacker has already answered: Can these exposures be chained into a viable path to something critical? Visibility across hybrid and multi-cloud environments remains patchwork at best; attackers move freely across boundaries that defenders frequently can’t see across. Identity exposure, overprivileged service accounts, stale credentials, misconfigured trust relationships, creates lateral movement pathways that go undetected until someone is already deep inside the environment. Alert overload causes security teams to spend disproportionate time on findings with no realistic exploitation path. None of this surprises working security professionals. What’s less widely acknowledged is that it’s not a resourcing problem. More analysts and more siloed tools, layered onto a fragmented architecture, produce more of the same. Security tools are built to detect and flag. They weren’t built to show you what an attacker sees when looking at your environment. Attackers have already leveraged automation to extend their reach. AI will enable them to exploit attack paths with unprecedented speed. So, as clichéd as it sounds, defenders need to put themselves in the shoes of attackers and adjust their approach from there. How defenders can change the equation That mindset shift starts with asking different questions. Most security programs are built around “what vulnerabilities exist?” The better question is “what can an attacker actually do with what’s in my environment right now?” That reframing has real consequences for how programs are run. Incident response speed matters, but it’s a downstream variable. The upstream question is how to make incidents caused by structural gaps and flaws less likely, which requires understanding your environment the way an attacker would, as a network of relationships that can be chained, not as a collection of independent assets and controls. Most security teams have never mapped their environment from that vantage point. Most attackers have. It also means prioritizing remediation by real exploitability rather than CVSS score or asset criticality in isolation. This is Exposure Management 101, the “EM” in Gartner’s Continuous Threat Exposure Management framework, which provides a structure for replacing broken vulnerability management processes. Exposure Management operationalizes the “think like an attacker” ethos at scale. Security programs that prioritize real exploitability are working on the right problem. The 2025 Verizon DBIR found that the median time for edge device vulnerabilities to be mass-exploited was zero days, while organizations took a median of 32 days to fully remediate them. And separately, the average time to patch across 17 high-profile edge device CVEs was 209 days. You can’t close that gap by triaging everything equally. The defender’s actual advantage: Know thy environment There’s a version of the current threat landscape that leads to fatalism. Why invest in a fight you’re structurally losing? It’s easy to go there, but it’s the wrong read. Ultimately, I believe that defense will become equally automated, a true battle of the machines. But even before we get there, defenders have a structural advantage that no amount of adversarial AI eliminates: They operate inside the environment they’re protecting. They can see the full topology, the identity relationships, the compensating controls, the critical assets. An attacker, however sophisticated the tooling, has to discover all of that from the outside. Defenders already know it. At least they should. Most organizations have the underlying data to understand their own exposures. The challenge is synthesizing it into something actionable, seeing on a continuous basis what an attacker would see, and which paths actually lead somewhere dangerous. Start with visibility that actually crosses the boundaries your tool stack has carved out over years of reactive purchasing. Get serious about prioritization based on what’s genuinely exploitable in your environment, not what scores highest on a spreadsheet. And stop conflating compliance-driven tests with your current risk posture, they tell you what things looked like last quarter, not today. The conversations CISOs should be having at the board level should focus on whether the program running today can flag when an AI-empowered attacker has a clear path to the company’s crown jewels. The industrialization of exploitation is a genuine shift in the adversary’s economics and logistics. But the structure of the problem hasn’t changed. Defenders who understand their own environment better than attackers, and who build their programs around that advantage, are in a stronger position than the threat headlines suggest. Are you leveraging the defender’s advantage? The fast way to know this is to have your team answer the following questions: How many critical corporate assets have a validated attack path from an internet-facing entry point? How has that number changed quarter-over-quarter? What percentage of our remediation effort closed an actual path versus a theoretical finding? Do we know the ways an attacker could create an attack path to our critical assets? Are we continuously assessing all of the possible attack paths to our critical assets?” Then, if you don’t like the answers, it’s time to revisit your control architecture. The best way to avoid cyber disruption from adversarial AI is to fix the structural problems so those attack paths aren’t realized in the first place. Carpe Diem! This article is published as part of the Foundry Expert Contributor Network. Want to join?
Roundcube Webmail Vulnerability Allows Hackers to Execute Malicious SQL Queries

gbhackers.com · 4 months ago

Roundcube Webmail users are being urged to update their systems immediately after the disclosure of multiple security vulnerabilities, including a critical pre-authentication SQL injection flaw that allows attackers to execute malicious database queries without requiring login access. The vulnerabilities were patched in newly released versions 1.6.16 and 1.7.1, published on May 24, 2026, as part
JINX-0164 Targets Cryptocurrency Firms with Fake Recruiter Lures and macOS Malware

thehackernews.com · 4 months ago

A new campaign orchestrated by a previously undocumented threat actor has targeted cryptocurrency organizations with an aim to facilitate digital asset theft using recruitment-themed social engineering and bespoke macOS malware. "These campaigns leveraged sophisticated social engineering techniques, custom macOS malware, and deep targeting of CI/CD infrastructure," Wiz researchers Shira Ayal