GMO Flatt Security's 'Takumi byGMO Guard' Exceeds 20 Million Package Downloads Per Day
GMO Flatt Security announced that the 'Guard' function of its security AI agent, 'Takumi byGMO', surpassed 20 million daily package downloads on May 19, 2026. The proxy tool, which automatically blocks malicious packages before installation, saw its usage double in just about a month driven by heightened risk awareness regarding supply chain attacks and the rise of AI-assisted coding.
📋 Article Processing Timeline
- 📰 Published: May 20, 2026 at 19:01
- 🔍 Collected: May 20, 2026 at 10:31
- 🤖 AI Analyzed: May 23, 2026 at 00:29 (61h 57m after Collected)
GMO Flatt Security Inc. (President and CEO: Yasutaka Ide, hereinafter 'GMO Flatt Security'), a company operating cybersecurity-related businesses for product development organizations under the mission of 'having engineers' backs' within the GMO Internet Group, announced that the 'Guard' function of its security AI agent 'Takumi byGMO' (hereinafter 'Takumi'), which launched in March 2026, recorded over 20 million package downloads per day on May 19. After reaching 10 million in early April, the number has doubled in just about a month, indicating that the 'Guard' function is rapidly being adopted as a new foundation for 'border control' at development sites.
What is the 'Guard' Function: Blocking Malicious Packages Before Installation
The 'Guard' function acts as a proxy intervening between package registries and engineers' development environments. It verifies the presence of malicious content in real-time when a package is downloaded. Packages determined to be malicious are automatically blocked before reaching developers' terminals or CI/CD environments. Implementation is completed simply by executing a single command line in the terminal, requiring no changes to existing code or operational procedures.
Most SBOM management tools rely on mechanisms that post-scan already installed packages, meaning they could not prevent the actual intrusion of malware. However, in the 'axios' compromise incident that occurred in March, even though the malicious version was published on npm for only about 3 hours, development environments that performed normal installation operations during that short window suffered widespread damage. Because the 'Guard' function intervenes at the time of installation, it prevents the intrusion of such malicious packages proactively.
Currently, it supports npm as well as PyPI and RubyGems, enabling cross-ecosystem defense across major package ecosystems, and is available for free to anyone, whether individual or corporate. Additionally, a batch setup feature using a management tool (paid) is provided for corporate clients considering bulk implementation across organizational devices.
Background of Surging Adoption: Heightened Crisis Awareness Due to Successive Software Supply Chain Attacks
The rapid adoption of the 'Guard' function is believed to be heavily related to the software supply chain attacks that occurred in quick succession in 2026.
At the end of March 2026, 'axios', an HTTP client library with 100 million weekly downloads, was compromised, causing widespread impact including on indirect dependencies. The breach originated from a social engineering attack on a single maintainer, becoming a sensational case where the compromise of a single prominent package posed risks to systems worldwide.
Furthermore, the proliferation of coding agents is amplifying the risk of cyberattacks. A 'structural problem' has emerged where AI can autonomously install packages without bearing responsibility, ultimately shifting the burden to the human side that must verify safety. Particularly with the popularization of 'vibe coding'—where development proceeds solely through instructions to AI without users writing code themselves—there is an increasing number of cases where users without development experience accept AI proposals as is, inadvertently relying on packages with insufficient safety verification.
In response to these successive breaches, awareness of countermeasures against software supply chain attacks in development environments has risen. The daily download count for the 'Guard' function consistently exceeded 10 million since early April 2026, reaching over 20 million by May 19.
Attacks on the software supply chain are expected to continue becoming more sophisticated and persistent, making 'border control' defenses essential moving forward. Driven by this crisis awareness, the adoption of 'Takumi' features, including the 'Guard' function, is expanding, primarily among security-conscious development organizations.
What is the 'Guard' Function: Blocking Malicious Packages Before Installation
The 'Guard' function acts as a proxy intervening between package registries and engineers' development environments. It verifies the presence of malicious content in real-time when a package is downloaded. Packages determined to be malicious are automatically blocked before reaching developers' terminals or CI/CD environments. Implementation is completed simply by executing a single command line in the terminal, requiring no changes to existing code or operational procedures.
Most SBOM management tools rely on mechanisms that post-scan already installed packages, meaning they could not prevent the actual intrusion of malware. However, in the 'axios' compromise incident that occurred in March, even though the malicious version was published on npm for only about 3 hours, development environments that performed normal installation operations during that short window suffered widespread damage. Because the 'Guard' function intervenes at the time of installation, it prevents the intrusion of such malicious packages proactively.
Currently, it supports npm as well as PyPI and RubyGems, enabling cross-ecosystem defense across major package ecosystems, and is available for free to anyone, whether individual or corporate. Additionally, a batch setup feature using a management tool (paid) is provided for corporate clients considering bulk implementation across organizational devices.
Background of Surging Adoption: Heightened Crisis Awareness Due to Successive Software Supply Chain Attacks
The rapid adoption of the 'Guard' function is believed to be heavily related to the software supply chain attacks that occurred in quick succession in 2026.
At the end of March 2026, 'axios', an HTTP client library with 100 million weekly downloads, was compromised, causing widespread impact including on indirect dependencies. The breach originated from a social engineering attack on a single maintainer, becoming a sensational case where the compromise of a single prominent package posed risks to systems worldwide.
Furthermore, the proliferation of coding agents is amplifying the risk of cyberattacks. A 'structural problem' has emerged where AI can autonomously install packages without bearing responsibility, ultimately shifting the burden to the human side that must verify safety. Particularly with the popularization of 'vibe coding'—where development proceeds solely through instructions to AI without users writing code themselves—there is an increasing number of cases where users without development experience accept AI proposals as is, inadvertently relying on packages with insufficient safety verification.
In response to these successive breaches, awareness of countermeasures against software supply chain attacks in development environments has risen. The daily download count for the 'Guard' function consistently exceeded 10 million since early April 2026, reaching over 20 million by May 19.
Attacks on the software supply chain are expected to continue becoming more sophisticated and persistent, making 'border control' defenses essential moving forward. Driven by this crisis awareness, the adoption of 'Takumi' features, including the 'Guard' function, is expanding, primarily among security-conscious development organizations.
FAQ
「Takumi byGMO」の「Guard」機能とは何ですか?
パッケージレジストリと開発環境の間に介在し、悪意あるパッケージをインストール前に自動でブロックするプロキシ機能です。
「Guard」機能の導入実績はどのようになっていますか?
2026年5月19日に1日あたりのパッケージダウンロード数が2,000万件を突破しました。4月上旬から約1ヶ月で倍増しています。
SBOM管理ツールと「Guard」機能の違いは何ですか?
SBOM管理ツールがインストール後の事後スキャンであるのに対し、「Guard」機能はインストール時にリアルタイム検証を行い、侵入そのものを未然に防ぐ点が異なります。
「Guard」機能はどのようなパッケージエコシステムに対応していますか?
現在、npm、PyPI、RubyGemsに対応しており、主要なパッケージエコシステムを横断した防衛が可能です。
「Guard」機能の導入が急増している背景は何ですか?
2026年の「axios」侵害などサプライチェーン攻撃の増加や、AIコーディング(バイブコーディング)の普及により、安全性の検証が不十分なままパッケージをインストールするリスクが高まっているためです。