<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>LLM on GMO Flatt Security Research</title>
    <link>https://flatt.tech/research/tags/llm/</link>
    <description>Recent content in LLM on GMO Flatt Security Research</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flatt.tech/research/tags/llm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Poisoning Claude Code: One GitHub Issue to Break the Supply Chain</title>
      <link>https://flatt.tech/research/posts/poisoning-claude-code-one-github-issue-to-break-the-supply-chain/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/poisoning-claude-code-one-github-issue-to-break-the-supply-chain/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; ( &lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security researcher at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;After publishing my previous article ( &lt;a href=&#34;https://flatt.tech/research/research/posts/pwning-claude-code-in-8-different-ways&#34;&gt;Pwning Claude Code in 8 Different Ways&lt;/a&gt;&#xA;), I continued investigating Claude-related products and found several more vulnerabilities.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I will explain a vulnerability in Claude Code&amp;rsquo;s GitHub Actions that could allow an attacker to compromise any repository that uses the Claude Code workflow, including Anthropic&amp;rsquo;s own repositories.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Variants of the misconfiguration issues described in this article were &lt;a href=&#34;https://github.com/cline/cline/security/advisories/GHSA-9ppg-jx86-fqw7&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;actively exploited&lt;/a&gt;&#xA; &lt;a href=&#34;https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation#attack-5-ambient-codeplatform---ai-prompt-injection&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;in the wild&lt;/a&gt;&#xA; before this article was published.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pwning Claude Code in 8 Different Ways</title>
      <link>https://flatt.tech/research/posts/pwning-claude-code-in-8-different-ways/</link>
      <pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/pwning-claude-code-in-8-different-ways/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; (&lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;A few months ago, I came across an interesting behavior while using Claude Code—it executed a command without my approval.&lt;/p&gt;&#xA;&lt;p&gt;Since I wasn&amp;rsquo;t using the permission bypass mode, I decided to investigate further to understand why it was able to execute commands without explicit approval.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;I discovered 8 ways to execute arbitrary commands in Claude Code without user approval.&lt;/p&gt;</description>
    </item>
    <item>
      <title>LLM App Security: Risk &amp; Prevent for GenAI Development</title>
      <link>https://flatt.tech/research/posts/llm-application-security/</link>
      <pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/llm-application-security/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m Sato (&lt;a href=&#34;https://x.com/Nick_nick310&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@Nick_nick310&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In recent years, the evolution and widespread adoption of Large Language Models (LLM) have been remarkable, and they are being utilized as generative AI in many services and business processes. While LLMs bring significant benefits, new security risks stemming from their characteristics have also been pointed out, making sufficient understanding and countermeasures essential for safe utilization. What kind of security challenges might arise when integrating LLMs into your company&amp;rsquo;s services and operations?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Securing LLM Function-Calling: Risks &amp; Mitigations for AI Agents</title>
      <link>https://flatt.tech/research/posts/securing-llm-function-calling/</link>
      <pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/securing-llm-function-calling/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello. I’m Yamakawa (&lt;a href=&#34;https://x.com/dai_shopper3&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@dai_shopper3&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security, Inc.&lt;/p&gt;&#xA;&lt;p&gt;LLMs exhibit high capabilities in various applications such as text generation, summarization, and question answering, but they have several limitations when used alone. Fundamentally, a standalone model only has the function of generating strings in response to input natural language. Therefore, to create an autonomous AI based on an LLM, a means to exchange information with the outside and execute concrete actions is necessary.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Risks of LLM Frameworks with Case Studies</title>
      <link>https://flatt.tech/research/posts/llm-framework-vulns-exposed/</link>
      <pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/llm-framework-vulns-exposed/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello. I’m Mori (&lt;a href=&#34;https://twitter.com/ei01241&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ei01241&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security, Inc.&lt;/p&gt;&#xA;&lt;p&gt;In recent years, the evolution of Large Language Models (LLMs) has accelerated the development of a wide range of AI applications, such as chatbots, data analysis/summarization, and autonomous agents. &lt;strong&gt;LLM frameworks&lt;/strong&gt; like LangChain and LlamaIndex abstract LLM collaboration and external data connections to improve development efficiency, but behind this convenience lie new security risks.&lt;/p&gt;&#xA;&lt;p&gt;In this article, we will explain common vulnerabilities that tend to occur when using or developing LLM frameworks, illustrated with specific CVEs, and learn lessons from each vulnerability. We will also introduce countermeasures that developers should be aware of based on these lessons.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
