BoletimSec•July 29, 2026•🇵🇹Translated from Portuguese

Cybercriminals Hide Malware in Fake Claude Code Installation Command Targeting macOS Developers

Cybercriminals are hiding malware inside a fake installation command for Claude Code, targeting developers on macOS. The campaign uses sponsored advertisements and counterfeit web pages to reach users searching for legitimate setup instructions.

The attack begins when a victim searches for installation guidance and clicks a sponsored result that mimics official documentation. The fraudulent page displays a step-by-step tutorial and directs the user to copy and paste a command directly into the macOS Terminal.

The command employs obfuscation techniques, including Base64 encoding, to conceal the address of the attacker-controlled server. It also disables digital certificate validation during the connection, allowing the download to proceed without security checks.

After execution, the command retrieves MacSync, an infostealer designed to harvest sensitive data stored on macOS systems. The malware specifically targets passwords, session cookies, SSH keys, cloud service credentials, and configuration files commonly used by developers.

Stolen authentication tokens can enable attackers to access user accounts and code repositories without triggering multi-factor authentication prompts.

Users are strongly advised to install Claude Code only through official documentation and to avoid any commands that hide URLs or disable security validations. Anyone who has already run the malicious instruction should isolate the affected Mac, revoke active sessions, and change all passwords, tokens, and SSH keys from a trusted device.

Related articles

AntiMalware•Malware & Botnets

MegaFon Reports 34% Rise in Russian Mobile Malware Infections Driven by Android Trojans

MegaFon monitoring data shows a 34% year-over-year increase in Russian users with detected mobile malware during summer 2026, with the sharpest spike of 77% recorded in August. The growth is primarily attributed to Android trojans capable of installing apps without user consent, intercepting notifications, enabling remote access, and stealing personal data. At the same time, blocked suspicious calls dropped significantly, by 31% in June, 41% in July, and 75% in August, which the operator links to state and corporate anti-fraud measures. Scammers are adapting by hijacking messenger accounts through social engineering, malware, and even rental schemes, often combining calls with fake app installations that deploy spyware. Phishing remains active, with 30% of detected malicious resources tied to investments and crypto, 21% to social networks and messengers, and 9% to harmful APK files. Director Sergey Khrenov noted that smartphones are increasingly used as tools by the attackers themselves in these hybrid schemes.

Securitylab•Malware & Botnets

Reflective DLL Injection: How Malware Executes DLLs Directly in Memory Without Disk Files

Reflective DLL Injection allows malicious code to load and execute a DLL entirely in memory, bypassing traditional file-based loading mechanisms on Windows. The technique uses a custom loader inside the DLL itself to handle PE format parsing, relocations, imports, TLS, and exception handling without calling LoadLibrary. Unlike standard loading, the resulting module often resides in MEM_PRIVATE regions and does not appear in conventional module lists, complicating forensic analysis. Tools such as Meterpreter and Cobalt Strike have historically employed reflective loaders, though Beacon Object Files represent a different COFF-based approach. Investigators must examine memory regions, thread start addresses, and Sysmon events 7, 8, and 10 rather than relying solely on file artifacts. The method does not bypass DEP, Arbitrary Code Guard, or access-control restrictions and leaves detectable traces when combined with behavioral indicators. Proper detection requires correlating private executable memory with process behavior and avoiding over-reliance on simplified signatures.

Habr•Malware & Botnets

Leaked DarkSword iOS Exploit Chain 'P7' Now Steals Crypto Wallet Seeds and Keystores

A third build of the P7 variant of the leaked DarkSword iOS exploit chain has been identified, featuring a new lure site themed around Chinese online casinos and a fresh command server. The chain exploits six vulnerabilities, including three zero-days, to deploy an implant that decrypts the keychain directly on the device and extracts seed phrases from wallets such as imToken, Trust Wallet, and Phantom. Unlike the original GHOSTBLADE, P7 rewrites the C2 agent to focus exclusively on wallet data while retaining the core TaskRop and MIG-filter bypass modules. Passive analysis of public sources also uncovered the long-running 'qqtime' delivery cluster that pairs DarkSword with the older Coruna chain for broader iOS coverage. The operator uses channel codes to support multiple affiliate distributors and employs an AppleKeyStore oracle to decrypt keychain items locally before exfiltration.

BoletimSec•Malware & Botnets

Censys Exposes DarkSword iOS Exploit Platform and Coruna Crypto Wallet Stealer

Censys has disclosed the inner workings of DarkSword, a commercial platform that sells remote access to iOS devices, along with its associated malware Coruna that targets cryptocurrency wallet recovery keys. The infrastructure was exposed between September 15 and 17, allowing researchers to analyze the full attack chain starting from a WebKit and JavaScriptCore exploit delivered through the browser. After escaping the Safari sandbox and reaching the kernel, the platform deploys three layers including a flag, controller, and main implant. Coruna then scans the device for BIP39-compliant seed phrases stored in photos and Apple Notes across 19 targeted wallet applications such as MetaMask, Phantom, Trust Wallet, Coinbase, Exodus, imToken, Bitpie, and BitKeep. The exposed server contained 11 victim recovery keys, 179 directories of extracted data, and 75 operator accounts, indicating a structured commercial operation with agent accounts, commissions, and device quotas. Confirmed infections affect devices running iOS 16.1 and 16.3.1, while Apple has extended patches to additional iOS 18 devices. Maintaining updated iOS versions remains the primary defense against this threat.