惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
F
Fortinet All Blogs
Microsoft Azure Blog
Microsoft Azure Blog
腾讯CDC
Vercel News
Vercel News
Recent Announcements
Recent Announcements
博客园 - Franky
小众软件
小众软件
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Cloudflare Blog
宝玉的分享
宝玉的分享
I
InfoQ
博客园 - 聂微东
Jina AI
Jina AI
J
Java Code Geeks
V
V2EX
U
Unit 42
Stack Overflow Blog
Stack Overflow Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
阮一峰的网络日志
阮一峰的网络日志
L
LangChain Blog
T
The Blog of Author Tim Ferriss
量子位

Truesec

CRA Reporting Starts on 11 September: What Businesses Need To Know - Truesec Privilege Escalation Vulnerability in Falcon Crowdstrike - Truesec SonicWall Vulnerabilities Exploited in the Wild - Truesec Privileged Access Management (PAM) Is No Longer Optional  - Truesec Australian Arrests Allegedly Disrupt TeamPCP, but the Shai-Hulud Threat Persists - Truesec DDoS Attacks Against Norwegian Government Sites - Truesec Critical Citrix NetScaler Memory-Overflow Vulnerability - Truesec Iranian Cyberattacks Against Critical Infrastructure - Truesec Russia Targets Businesses and Officials Behind Europe’s Ukraine Defense Supply Chain - Truesec The World Is Moving at Machine Speed. Are We Ready? - Truesec False CVE in Overwhelmed Verification System - Truesec LLMjacking Is a New Cyber Threat - Truesec Rogue AI Agent Allegedly Hack Hugging Face - Truesec Microsoft SharePoint Server Vulnerabilities Actively Exploited - Truesec Russian Intelligence Targets SOHO Routers - Truesec Cyber Warfare in the Iran War - Truesec Organized Cybercrime Merging with Other Crime - Truesec The Fortibleed Campaign: Truesec's Experience Fortibleed: Truesec's Experience Supply Chain Attack Compromising Arch Linux AUR Packages with Infostealer and Rootkit - Truesec FortiNet SSO Vulnerability CVE-2025-59718 and CVE-2025-59719 Leading to Full System Compromise - Truesec Critical Vulnerabilities in Ivanti Sentry Allows Code Execution as Root (CVE-2026-10520 & CVE-2026-10523) Typosquatting: When Your Domain Is Used Against You AI in Cybersecurity: Separating Operational Reality from Speculation Compromised @redhat-Cloud-Services Npm Packages Distribute Credential-Stealing Worm GitHub Hacks Highlights Need for Repository Security Installation of a Syslog Log Collector Critical Cisco Secure Workload Vulnerability Allows Unauthenticated Site Admin Access (CVE-2026-20223) Securing IT, OT, and IoT When the Digital Meets the Physical Russia Rolls Out Surveillance Through State-Backed “Super App” MAX
AI Used in Ransomware Attack
jennie mattar · 2026-07-03 · via Truesec

Threat Insight

Researchers have found what they believe is the first ransomware attack carried out from start to finish by an AI agent. An operator they dubbed “Jadepuffer” used an LLM to handle most of the attack sequence, including gaining access, stealing credentials, moving laterally, and finally encrypting the victim’s production database.

AI ATTACK CYBER

The initial attack vector was the exploitation of a known missing-authentication vulnerability, CVE-2025-3248, in Langflow, an open-source tool for building AI apps and agent workflows. Once inside, the agent moved quickly and cleaned up after itself. It mapped the machine, then searched it for secrets: API keys for AI services such as OpenAI, Anthropic, DeepSeek, and Gemini, cloud credentials for Chinese providers such as Alibaba and Tencent, alongside AWS, Google, and Azure crypto wallet keys and database logins.

It then pivoted to a separate, internet-facing server running a MySQL database and Alibaba’s Nacos, a configuration and service directory common in microservices environments. The threat actor logged into the database as root. They then encrypted all 1,342 Nacos settings, dropped the original tables, and left a ransom note demanding Bitcoin with a Proton Mail contact.

The threat actor generated a random encryption key, printed it to the screen once, and never saved or sent it anywhere, essentially making it impossible to decrypt the impacted data.

The clearest sign that the attack involved the use of AI was the code itself. The attack payloads were full of plain-English notes explaining why each step was being taken: a running commentary that a human hacker would likely never bother to write, but that a model may produce by default.

The attacker also responded very quickly to problems as they arose. In one case, it went from a failed login to a correct, multi-step fix in 31 seconds, diagnosing the exact cause instead of blindly retrying, suggesting that an AI agent may have been involved. [1]
Assessment

There is not enough information to determine whether this attack was indeed conducted solely by an AI agent, as the researchers claim, or whether it was carried out by a human operator using an AI tool and evaluating each step before issuing new instructions to the AI.

The attack did not display any particular sophistication, quite the opposite. The vulnerability exploited was over a year old, and the ransomware encryption was poorly implemented, meaning the victim would not have been able to recover the files even if they had paid the ransom. This is a critical mistake for a serious ransomware operator.

Using AI to automate part or all of the attack chain is also more of an evolution than a revolution in ransomware. Some ransomware groups that specialize in attacking smaller victims used scripts to automate their attacks long before AI became widely used. The smaller the environments, the easier it is to automate attack sequences. The cybercriminals’ business model relies on a large volume of victims and can remain profitable even if many attacks fail.

Nevertheless, the attack shows how the use of AI can lead to faster, if still unsophisticated, attacks that give victims less time to react.

References

[1] https://www.sysdig.com/blog/jadepuffer-agentic-ransomware-for-automated-database-extortion