
What happened
Check Point Research found Aokigahara, which carries a dedicated "aisessions" feature that hunts login files, tokens and session data for desktop ChatGPT, Claude, Codex, Cursor, Windsurf, GitHub Copilot and Gemini CLI, then uploads stolen data to its command-and-control server.
Why it matters
One infected laptop can hand attackers working logins to AI chats, code repositories and cloud accounts at once, raising risks of leaked private conversations and source code or paid AI services being misused.
WHO IT HITSCorporate security and IT teams, especially those supporting software developers, may need to treat AI tool credentials and sessions as sensitive identity assets alongside browser and cloud logins. Developer workstations become the focal point, since a single compromised machine can expose AI assistants, code repositories and cloud environments at once.
Summaries like this, every morning.
Check Point Research describes Aokigahara as arriving at a moment when AI assistants sit alongside source code, cloud services and sensitive business information. The malware keeps its AI-focused and developer-focused functions as separate modules, so the research does not conclude that attackers are deliberately combining them into a single campaign. What the shared codebase does show, in Check Point's reading, is how many high-value access paths now live on a modern developer's device.
The firm frames the finding as a shift in what information stealers pursue. For years these programs went after passwords, browser sessions, financial data and crypto assets; now that employees routinely log into AI assistants connected to company data, source code and cloud environments, those AI sessions and credentials become another identity asset worth stealing, according to the research.
Check Point's head of research, Eli Smadja, argued that AI credentials and sessions should be handled like browser sessions, cloud credentials and developer keys rather than as secondary application data. The firm said the findings change the premise of corporate AI security discussions: companies need to protect the credentials, tokens and authenticated sessions used to reach AI services, not just the information employees type into them, and should check AI sessions when an endpoint is compromised.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Upwind Security raised $400 million in a Series C led by Bessemer Venture Partners, with Greylock Partners, Sa…

Anthropic gathered 61 causal-inference experts to judge a farm-support case

Instagram head Adam Mosseri said on the Colin and Samir podcast that frustration and anger about AI is "not on…

Cisco released Project Quarry, an open-source engine that evaluates whole AI agent sessions — single- and mult…

Morgan Stanley's Institute for Sustainable Investing polled 900 institutional investors across North America…

Researchers warn that cyber attacks on law firms are surging, with AI cited as a driver, Reuters reports
