Security firm Genians reported on 10 August that it found a working offline LLM stack inside attack infrastructure attributed to North Korea's Kimsuky group: installation traces for Ollama, GPT4All and Msty, alongside Cursor and OpenAI's Whisper.

Retrieval pointed at stolen files

The detail that separates this from generic tool-hoarding is configuration. GPT4All's LocalDocs feature — local retrieval-augmented generation — was set up against stolen documents. That is an operator building a private question-answering system over exfiltrated material rather than reading it by hand.

The delivery chain

Genians calls the campaign Operation GitPower. Phishing messages carried ZIP archives containing LNK files, which launched PowerShell loaders and ended in AsyncRAT. GitHub repositories served as command-and-control storage for configurations, scripts and payloads. Targets included crypto and finance organisations.

Why local models matter here

Frontier labs enforce policy at the API: accounts get banned, prompts get flagged, abuse teams publish takedowns. A model running on the operator's own machine generates no telemetry at all. The enforcement chokepoint that OpenAI and Anthropic have leaned on for state-actor misuse simply does not exist for an Ollama install.

What was actually observed

This is vendor research, self-published and not independently replicated, and the evidence is installation traces and configuration. Genians' own language is that the actor is continuously preparing to integrate AI — not that a finished AI-driven attack tool was seen operating.

The capability is ordinary

None of the tooling is exotic. Ollama, GPT4All and Msty are consumer-grade runtimes any developer can install in minutes, serving openly published weights. That is the uncomfortable part: this operational upgrade needed no frontier-lab access, no stolen weights and no budget beyond a workstation.