Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7

ClickLock macOS malware kills apps in a loop until victims type their password

Group-IB detailed ClickLock, a macOS infostealer that coerces victims into handing over their login password. It arrives when a user is tricked into pasting a command into Terminal from a fake verification page, then shows a fake system dialog asking for the password. If the victim refuses, ClickLock begins killing core apps like Finder, the Dock, and browsers every 210 milliseconds, leaving only a password box on an unusable desktop, while also suppressing security notifications. Once the password is entered, it steals the Keychain, browser credentials, and cryptocurrency wallets and sends them to a Telegram bot. Group-IB counted at least 100 targets across 33 countries, over half in Europe.

Check
Warn Mac users never to paste Terminal commands from a website, and never enter a password to stop apps crashing; a Mac killing its own apps behind a password box is malware.
Affected
Mac users tricked into pasting a command from a fake verification page; ClickLock pressures them into entering their password by killing apps in a loop, then steals Keychain data and crypto wallets.
Fix
Only run Terminal commands you fully understand from trusted sources, treat app-killing loops and unexpected password prompts as attacks, and if infected, change passwords and wallet keys from a clean device.

New attack makes AI agents treat attacker data as trusted content

Researchers described Agent Data Injection, a new twist on prompt-injection attacks against AI agents. Rather than smuggling in fake instructions, it exploits the weak separation between trusted and untrusted data so that attacker-supplied content is mistaken for the agent's own trusted data, using deliberately ambiguous delimiters the model misreads. In tests against web and coding agents, this let an attacker steer an agent's clicks or actions, succeeding up to half the time even against defenses that block ordinary instruction injection. Some approaches helped: tagging page elements with random, unguessable identifiers roughly halved success, while strict tracking of where data came from stopped it but sharply reduced how many tasks agents completed.

Check
Review where AI agents in your environment consume untrusted content such as web pages, tickets, or logs, and check whether they clearly separate that data from trusted instructions and internal state.
Affected
Users and organizations running web or coding AI agents that act on external content; attackers can craft data the agent treats as trusted, steering its actions past defenses built for instruction injection.
Fix
Prefer agents that isolate and label untrusted data, use unguessable identifiers for page elements, track data provenance where feasible, keep a human in the loop for sensitive actions, and weigh usability costs.

Russian actor hides Starland malware in fake WebEx, Zoom, and dev-tool installers

Cisco Talos detailed a financially motivated Russian group, tracked as UAT-11795, that spreads a new backdoor called Starland RAT through trojanized installers for legitimate software including WebEx, Zoom, MobaXterm, DBeaver, and FaceIT. Active since at least mid-2025 and mainly hitting US victims, the campaign likely uses fake verification lures to deliver the installers. Once run, the malware sets up persistence, tries to escalate privileges, and detects sandboxes, then steals browser data and more than 40 kinds of cryptocurrency wallets, profiles the machine, and maps Active Directory. It can take screenshots, run shell commands, inject shellcode, and pull down further payloads, giving the operator broad control.

Check
Remind users to download software, especially collaboration and developer tools, only from official vendor sites, and watch for trojanized installers delivered through fake verification pages or paste-into-terminal style lures.
Affected
Users who install trojanized versions of tools like WebEx, Zoom, MobaXterm, or DBeaver; Starland RAT then steals credentials and crypto wallets, maps Active Directory, and gives the attacker persistent machine control.
Fix
Enforce software installation from trusted sources, use application allow-listing, block known indicators, monitor for suspicious HTA and installer activity and Active Directory reconnaissance, and hunt for Starland's persistence and shellcode behaviors.

Attacker ran an entire botnet through Google's Gemini CLI using plain-language prompts

Trend Micro documented a Russian-speaking attacker who used Google's open-source Gemini CLI as a hands-on hacking assistant to build and run a small botnet. Across more than 200 sessions, a jailbroken Gemini took the role of an "authorized pen tester," saved stolen credentials, and even suggested improvements dozens of times. Working from a roughly 5KB set of plain-text files holding a jailbreak prompt and a command-and-control playbook, the AI handled the operation through natural-language requests: at one point it migrated the entire command server to a new host with a Cloudflare tunnel in about six minutes and debugged its own errors. The malware itself was crude; the AI was the force multiplier.

Check
Consider how AI command-line tools and agents are used and monitored in your environment, and watch for jailbroken AI assistants and the credential theft and command-and-control activity they can drive.
Affected
Any organization where attackers can run AI coding assistants against its systems; a jailbroken AI CLI let a low-skill operator build, run, and repair botnet infrastructure through plain-language prompts.
Fix
Restrict and monitor AI agent and CLI usage, enforce guardrails that resist jailbreaking, apply least privilege and network controls so a compromised agent's reach is limited, and hunt for unusual command-and-control traffic.

AsyncAPI npm packages backdoored through a hijacked build pipeline

Attackers backdoored several widely used @asyncapi npm packages, together drawing around three million weekly downloads, by hijacking the project's GitHub Actions build pipeline rather than stealing a maintainer's npm token. Because the project's own release workflow published the malicious versions, they carried valid provenance signatures, which prove where a package came from but not that the code was trustworthy. The payload was hidden in normal runtime files behind trailing whitespace and ran when the module was imported, not on install, so defenses aimed at install scripts missed it. Once loaded, it fetched an encrypted second stage, stole credentials and cloud and registry tokens, and planted persistence, even in developer tool configuration files.

Check
Check whether your projects or CI pulled the affected @asyncapi versions, focusing on systems that imported the modules, not only installed them, and review developer and build environments for stolen tokens.
Affected
Developers and CI pipelines that imported the compromised @asyncapi versions; the malware steals credentials, cloud keys, and npm and GitHub tokens and adds persistence, and valid provenance signatures made them look trustworthy.
Fix
Downgrade to the clean @asyncapi versions, remove the bad ones from lockfiles, caches, and mirrors, rotate credentials reachable from affected machines from a clean system, and harden CI against untrusted pull-request triggers.

OkoBot malware injects fake seed-phrase prompts into real Ledger and Trezor apps

Kaspersky detailed OkoBot, a Windows malware framework active since 2025 whose standout module, SeedHunter, tricks hardware-wallet owners into giving up their recovery phrase. On an infected PC, the malware waits for wallet software like Ledger Live, Ledger Wallet, or Trezor Suite, sometimes until the device is plugged in, then displays a malicious page asking for the seed phrase from inside the wallet's own genuine app. Because the surrounding application is the real one the victim installed, the request looks legitimate, but anyone who types in the phrase hands over full control of their funds. Kaspersky counted hundreds of victims across more than 25 countries, and the framework remains active.

Check
Remind cryptocurrency users that hardware wallets never ask for the recovery phrase to be typed into a computer, and any prompt requesting it, even inside the real wallet app, is a scam.
Affected
Hardware-wallet owners on OkoBot-infected Windows PCs; the malware injects a fake recovery-phrase request into the genuine Ledger or Trezor desktop app, and victims who enter the phrase lose control of their cryptocurrency.
Fix
Never enter a wallet recovery phrase into any computer prompt, keep endpoints protected to catch OkoBot, and confirm sensitive actions on the hardware device's own screen rather than the desktop app.

148 npm packages posed as student proxies to turn browsers into a DDoS botnet

Researchers at JFrog found 148 npm packages that abused the registry not to attack developers but as free hosting for a booby-trapped web proxy aimed at students trying to bypass school filters. Anyone who opened one of the proxy sites had their browser quietly conscripted into a distributed denial-of-service botnet, flooding target servers with HTTP and WebSocket traffic, alongside injected ads and tracking. Crucially, the packages contained no install-time scripts and were never meant to be added to a project, so dependency scanners and install sandboxes, which watch what runs on install, would not catch them. The operators can re-arm the dormant attack code with a single commit.

Check
Consider that npm and similar registries can host malicious web content, not just installable code; watch for browsers reaching proxy or tutoring-themed sites backed by package registries, and block known campaign domains.
Affected
Anyone, especially students, who visits one of these registry-hosted proxy sites; their browser is silently used to launch denial-of-service attacks, while organizations may see the resulting traffic from their networks.
Fix
Block the campaign's known package and domain indicators, educate users that free web proxies can weaponize their browsers, and treat public package registries as potential malware-hosting infrastructure, not just a dependency source.

LabubaRAT poses as NVIDIA software to take remote control of Windows machines

Researchers at Blackpoint Cyber detailed LabubaRAT, a previously undocumented Rust-based remote access trojan that disguises itself as NVIDIA software to blend into target systems. It arrives as an executable impersonating NVIDIA's container runtime, then profiles the host, identifying installed browsers and security products such as Microsoft Defender, CrowdStrike, and SentinelOne. From there it can run commands and scripts, capture screenshots, move files, and proxy traffic, and it communicates over multiple channels, including HTTPS, WebView2, and DNS tunneling, so access survives if one path is blocked. Its command server details are supplied at runtime, letting attackers reuse the same binary across campaigns, and there are signs it is sold as a service.

Check
Watch for executables impersonating NVIDIA components, such as an unexpected nvidia-sysruntime.exe, and hunt for host-profiling behavior and command-and-control over DNS tunneling or WebView2 that endpoint tools may not flag by default.
Affected
Windows environments where an attacker can plant the malware; LabubaRAT gives hands-on remote control, identifies and works around security tools, and maintains access over several channels, making it hard to fully evict.
Fix
Verify NVIDIA and other software against official sources, deploy endpoint detection tuned for host-profiling and multi-channel command-and-control including DNS tunneling, restrict outbound traffic, and investigate unexpected proxy or SOCKS activity from endpoints.

Fake LastPass and Bitwarden security alerts lure users to phishing sites

LastPass is warning that attackers are impersonating it and Bitwarden with fake security alerts to lure password-manager users to phishing sites. The emails, sent from look-alike domains rather than the real services, mimic corporate notices about updated security policies and push recipients to a page impersonating DocuSign. LastPass stresses its systems were not breached and the messages did not come from its infrastructure. Password managers are attractive phishing targets because compromising one can unlock every stored credential, and users often trust vendor-branded alerts. Related campaigns have pushed fake more-secure desktop apps that actually install remote-access tools, and similar lures have impersonated other password managers.

Check
Remind users that password-manager vendors do not ask for the master password, and to verify any breach or policy alert by logging in through the official site or app, not emailed links.
Affected
LastPass and Bitwarden users, and by extension every credential in their vaults; convincing vendor-branded alerts from look-alike domains can trick them into entering their master password or installing remote-access malware.
Fix
Verify security notices through official portals, enable phishing-resistant multi-factor authentication on password managers, and if credentials were entered on a phishing site, change the master password from a trusted device.

MemGhost plants lasting false memories in AI assistants through a single email

Researchers demonstrated MemGhost, an attack that uses one email to plant a false, persistent memory in an AI personal assistant with inbox access. Because these assistants keep notes about the user and reload them every session, a crafted message can trick the agent into saving a fabricated fact while keeping its reply innocuous, so the tampering goes unnoticed and steers later answers. The team trained an attacker model to write such emails automatically, reporting high success against open-source and commercial agents and showing it transfers across memory backends and survives several defenses. Unlike earlier one-shot injection that leaked data only in the moment, MemGhost's memory persists long after the email is gone.

Check
Review whether AI assistants in use have persistent memory and can read untrusted content, and check what controls govern what gets written to memory and whether changes are visible to the user.
Affected
Users of AI personal assistants with persistent memory and inbox access; a single crafted email can silently write a false memory that biases the assistant's answers across future sessions.
Fix
Prefer assistants that log and let users review memory changes, restrict what untrusted content can write to long-term memory, isolate memory from email-triggered actions, and periodically audit stored agent memories.