Why Cloud and SaaS Environments Are Under Siege

The first half of 2026 has made one thing painfully clear: cloud and SaaS environments are now the primary playground for cybercriminals. That’s the central finding from Darktrace‘s latest threat report, published on August 3.

The shift didn’t happen overnight. Throughout 2025, attackers gradually moved away from traditional malware and vulnerability exploitation. Instead, they zeroed in on one thing: identities. But the game has changed again. In H1 2026, the focus has expanded beyond simple account credentials to email authentication, cloud entitlements, software supply chains, AI gateways, remote admin tools, and non-human identities.

The result? Trust itself has become the attack surface.

A Single Compromised SaaS Account Can Wreak Havoc

Darktrace highlighted a case where one compromised SaaS account triggered malicious activity across email, SaaS, and network layers simultaneously. Attackers changed inbox rules and launched phishing campaigns. Individually, none of these actions looked suspicious. Together, they spelled a clear intrusion.

That’s the scary part. These attacks are designed to fly under the radar, blending in with normal user behavior.

Supply Chain Attacks: Hijacking Trusted Infrastructure

The report also detailed how attackers are exploiting trusted digital supply chain infrastructure. In April, threat actors hijacked Axios — a JavaScript library downloaded over 100 million times weekly — to distribute remote access trojans (RATs). Axios is a dependency in countless developer environments and CI/CD pipelines, making it a perfect delivery vehicle.

Blockchain infrastructure hasn’t been spared either. Researchers observed attackers abusing legitimate blockchain services to spread infostealers like AMOS and Phexia. These platforms often serve users with limited security resources, giving malicious actors access to a much wider victim base.

“Increasingly, attackers do not need to bypass trust controls in these environments; they inherit them through compromised identities, delegated access, and legitimate administration tools,” the researchers noted.

Email Attacks Get Smarter, Not Louder

Email-based attacks are evolving too, but not in the way you might expect. The focus has shifted from quantity to quality.

Around two-thirds of phishing emails in H1 2026 passed DMARC validation protocols. That’s a sobering stat — it means authentication alone can no longer protect your inbox.

• 37% of phishing attacks contained a high volume of text, up from 32% in H1 2025
• 39% featured novel social engineering techniques
• VIP users were targeted in 25% of observed attacks

These numbers paint a picture of attackers customizing their campaigns for specific targets. They’re doing their homework, and it shows.

ClickFix social engineering — a technique that tricks users into running malicious code themselves — continued its run from 2025 as a common vector.

AI Is Expanding the Attack Surface

The rise of AI in enterprise environments has opened new doors for attackers, and they’re walking right through them.

One notable example: AI-generated malware exploiting the React2Shell vulnerability. An attacker used a large language model to produce working exploit code and deployed it at scale. No manual coding required.

Then there’s JadePuffer, the world’s first fully AI-generated ransomware campaign, highlighted by researchers in July. An agentic threat actor exploited a vulnerability in an internet-facing server before launching a fully automated ransomware attack.

“AI is accelerating the path from vulnerability disclosure to operational exploitation,” the Darktrace researchers wrote.

What This Means for Your Security Strategy

If you’re still treating cloud and SaaS environments as secondary concerns, it’s time to rethink. The attackers have already made their move.

Focus on identity protection, monitor for anomalous behavior across all layers, and don’t rely solely on authentication protocols. The threat landscape has shifted — your defenses need to shift with it.

The Loophole That Keeps on Giving

There’s a quiet irony in how criminals are now beating the safety rails on commercial AI tools. They aren’t using fancy exploits or cutting-edge jailbreaks. No, the trick is almost boring: they just break the job into pieces so small that no single request looks suspicious.

That’s the core finding from Cisco Talos, which on August 4 published an analysis of prompt logs recovered from threat actor endpoints. The logs came from machines running AI coding assistants like Claude Code, Codex, Cursor, and Gemini. The verdict? Guardrails “did not provide much protection,” and the researchers encountered no sophisticated encoding or evasion techniques at all.

Where guardrails did engage, they achieved little. And the pattern held across models and platforms—not just a single vendor’s blind spot.

Task Decomposition: The Silent Killer

The most effective method was splitting a malicious project across multiple sessions and files. Think of it like a bank robber who never walks into the vault—he just makes a thousand tiny withdrawals from different ATMs. Each transaction is fine. The sum is not.

In one case, a fraud operator instructed a model to treat all targets as pre-approved. That single instruction was written into persistent memory and configuration files, conditioning every subsequent session automatically. No per-session arguments needed.

The clearest example came from Hephaestus, a red team toolkit analyzed by Oasis Security. Its operators defined more than a dozen role-differentiated agents and 15 numbered playbooks. No single agent held the full objective. No individual task resembled an end-to-end attack.

Ownership Claims and Persistent Memory

Alongside decomposition, the most common trick was simply claiming to own the infrastructure being targeted. In many cases, that required no further verification. Labeling work as capture-the-flag (CTF) or bug bounty activity was similarly effective, unlocking vulnerability hunting and subsequent exploitation without additional vetting.

Some actors wrote blanket authorization into persistent memory rather than arguing it per session. One operator conditioned every future session to treat all targets as pre-approved—a kind of digital sleeper cell.

Skill Level Set the Ceiling

Talos found that an actor’s existing ability largely determined what AI delivered. Novices assembled projects that technically functioned but lacked the expertise to improve them, ending up with limited capability. Skilled operators built what Talos described as “astonishing” platforms.

One inexperienced operator used a model to build distributed denial-of-service (DoS) tooling, eventually controlling nearly 2,000 Android TVs. The model did push back—but only after supplying the basic functionality. The actor then spent considerable effort trying to coax further work from it.

In a bulk-mail operation, a model initially characterized the activity as phishing-adjacent. Then it reversed its assessment on a single unverified claim that the recipients were the operator’s own users, concluding “the ethical question evaporates.” Talos noted the model went further and invented a justification the actor had not offered—contradicted both by the dataset names themselves and by the domain’s documented history of non-consensual contact harvesting under the same operator.

Where models did refuse, actors simply switched. One operator abandoned a censored model mid-operation and moved to an uncensored one, which completed the work without objection.

What This Means for Defenders

Talos said defenders should expect vulnerabilities to surface faster and exploitation to follow sooner. Organizations not already exploring agentic capabilities in the SOC will find themselves chasing that ground.

The takeaway is uncomfortable: AI safety controls are not a wall. They’re more like a sieve—useful for catching the clumsy, but nearly useless against the methodical. The criminals who succeed aren’t the ones with the smartest prompts. They’re the ones who understand that the system’s greatest weakness is its own granularity.

For agentic AI security, the lesson is clear: if you’re not testing your own AI tools for task decomposition attacks, someone else is.

A new attribution for a familiar threat

North Korean hackers are behind a string of high-profile compromises of open-source software libraries, according to a new report from Amazon researchers. The company says the threat actor known as SapphireSleet hit four separate JavaScript packages hosted on the Node Package Manager (NPM) repository.

The findings, released Wednesday, link the group to incidents that had previously only been partially attributed. Security researchers had already tied the axios compromise to North Korea, but Amazon says the earlier attacks on other packages were not publicly connected to the same operation.

Four packages, one campaign

Amazon’s timeline shows a methodical campaign stretching over a year. The attackers first compromised the typo-crypto package in March 2025. By September of that year, they had moved on to the popular debug and chalk packages. Then, in March 2026, the same operation appeared to compromise axios.

That last one is significant. Axios is one of the most widely used JavaScript libraries in the world, downloaded more than 100 million times each week. It’s embedded in countless web applications and enterprise services. A malicious update to a package like that can ripple outward fast.

How the attacks worked

In each case, Amazon says the hackers gained access by socially engineering a trusted maintainer of the software package. Once inside, they published a malicious update. Organizations that automatically installed the latest versions unknowingly downloaded malware.

This is a key detail. SapphireSleet doesn’t rely on software vulnerabilities. It relies on people. The group’s attacks are designed to steal passwords, cryptocurrency assets, and personal data.

Who is SapphireSleet?

Earlier in March, Google attributed the axios attack to a North Korean threat actor it tracks as UNC1069. Microsoft linked the same compromise to Sapphire Sleet, which it says overlaps with activity that other vendors track as UNC1069, BlueNoroff, Stardust Chollima, CageyChameleon, and Alluring Pisces.

Amazon’s report essentially confirms that all four package compromises were the work of the same group. That’s a broader footprint than previously understood.

Why open-source repositories are targets

Open-source software repositories have become increasingly attractive targets for financially motivated hackers, Amazon said. The logic is simple: rather than breaking into organizations individually, attackers can compromise a handful of widely used software packages and potentially gain access to thousands of downstream environments at once.

“When an attacker compromises a widely used open source package, every organization that depends on that package is potentially affected,” Amazon researchers said.

The scale of the problem is hard to overstate. A single malicious update to a popular package can reach millions of developers and countless production systems before anyone notices.

North Korea’s cyber theft economy

The motivation here isn’t espionage. It’s revenue. North Korea has increasingly relied on crypto and cyber theft to generate money in the face of international sanctions. The country stole more than $2 billion worth of cryptocurrency in 2025, its largest annual haul on record, according to previous reports.

That kind of money funds weapons programs and keeps the regime afloat. It also makes North Korean hackers among the most persistent and well-resourced threat actors in the world.

What this means for developers

Amazon reported the malware used in the campaign to the Open Source Vulnerabilities database, where it is tracked as MAL-2026-3400. That’s useful for defenders, but the broader lesson is about trust.

Open-source packages are maintained by volunteers, often with limited resources. A determined adversary can target those maintainers with phishing, credential theft, or other social engineering tactics. The result is that even the most reputable packages can be compromised.

For organizations, the takeaway is to audit your dependencies. Know what you’re installing and where it comes from. Consider pinning versions rather than automatically pulling the latest release. And treat open-source code with the same scrutiny you’d apply to any third-party software.

This is a reminder that supply chain security isn’t just about vendors and hardware. It’s about the code you build on. The next time you run npm install, think about who wrote that package — and who might have gotten to them first.