AI Weekly Malaysia

South Korean security firm Genians reports that North Korean threat group Kimsuky is running local LLMs via Ollama, GPT4All, and Msty, and experimenting with Cursor and RAG for local document search, keeping operations off cloud services to avoid detection. The group uses AI to craft polished phishing lures about virtual assets and finance, delivered via ZIP archives containing malicious LNK files that run PowerShell loaders, with GitHub repositories serving as command-and-control infrastructure.

Why: Threat actors are now using the same local LLM toolchain (Ollama, GPT4All, Cursor) that many developers and AI tinkerers run, meaning AI-generated phishing lures will be increasingly convincing and harder to spot. Builders should scrutinize unfamiliar GitHub repositories more carefully since Kimsuky uses public GitHub repos as C2 infrastructure, and treat unsolicited ZIP/LNK files—even those referencing research or events—as high-risk.

South Korean security firm Genians reports that North Korean hacking unit Kimsuky has set up an offline AI stack on its own infrastructure using Ollama, GPT4All, and Msty, with GPT4All's LocalDocs RAG database (localdocs_v3.db) configured to query a private document collection. The group has not trained a custom model but is assembling existing tools to automate malware development and improve phishing lures, which will increasingly lack the traditional tells of stilted translation and formatting errors.

Why: If you build or operate systems that rely on users spotting phishing by its clumsy language or formatting, that defense layer is eroding—AI-generated lures will read naturally. Shift detection toward correlating technical indicators like LNK execution, PowerShell activity, hidden scheduled tasks, and unusual GitHub traffic rather than judging emails by polish. For builders running offline LLM stacks (Ollama, GPT4All), note that these same tools are now documented in nation-state offensive operations.

Uber Freight is investigating a data breach claimed by the Helix extortion group, which says it stole nearly 1 million files from mailboxes, OneDrive accounts, and accounts receivable systems. Uber Freight says operations were never disrupted and the incident was contained. Helix is linked by Google Threat Intelligence to a cluster (UNC6671) that uses vishing—posing as IT helpdesk staff—to run device code phishing against employees, then siphons data from Microsoft 365 and Okta.

Why: If your org uses Okta or Microsoft 365, this is a concrete reminder that device code phishing via fake IT helpdesk calls is an active, working attack path—not a theoretical one. Train staff to reject unsolicited device code prompts and verify any 'mandatory security migration' call through an internal channel before entering codes.

Levi Strauss disclosed a data breach after social engineering attackers gained access to three employee workstations and exfiltrated corporate data. Google researchers are tracking a broader campaign (dubbed UNC6671) that has targeted 200+ organizations over five weeks, phoning employees on personal mobiles while posing as IT support and directing them to spoofed login pages that harvest credentials and MFA codes.

Why: If you ship MFA-protected systems, this campaign shows attackers are reliably bypassing MFA via real-time phishing pages reached through phone-based social engineering—not by breaking cryptography. Consider whether your auth flow supports phishing-resistant factors (FIDO2/passkeys) rather than OTP codes that can be relayed through a spoofed page, and brief teams that IT support will never call their personal mobile asking them to log into a portal.

A passenger on a Delta flight from Las Vegas to Atlanta after DEF CON is suspected of jamming the aircraft's in-flight Wi-Fi and broadcasting a fake network called 'Delta Wifi Fast,' possibly using a deauthentication attack and a device like a Wi-Fi Pineapple to phish passenger credentials. Delta confirmed the incident, stated no aircraft systems were affected, and said it is investigating with federal law enforcement.

Why: This is a cautionary incident about how trivially captive-portal Wi-Fi can be spoofed with off-the-shelf tools, but it does not require any change to what builders ship. If you build apps that handle authentication over public or shared Wi-Fi, treat untrusted network captive portals as hostile and never rely on network-level trust for credential entry.