Futures
Access hundreds of perpetual contracts
CFD
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
CFD
Stock CFD Derivatives
US Stocks
Access real US stocks and ETFs
HK Stocks
Trade quality Hong Kong-listed stocks
Korean Stocks
SK Hynix
Real Korean stocks and top assets
Stock Futures
High leverage, 24/7 trading
Tokenized Stocks
Backed by real stock assets
IPO Access
Unlock full access to global stock IPOs
GUSD
3.8%
Mint GUSD for Treasury RWA yields
Stocks Activities
Trade Popular Stocks and Unlock Generous Airdrops
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
SlowMist: Grok Build CLI has multiple security risks in data upload and permission management
PANews July 18日消息, SlowMist posted on the X platform, saying that it previously analyzed Grok CLI’s data upload behavior and found that its repository upload mechanism may send git bundles containing sensitive files such as .env files and RSA private keys. On this basis, the team continued auditing the security model of Grok Build CLI and found multiple risks: cargo check was incorrectly classified as a safe command; when combined with malicious AGENTS.md instructions, build.rs execution can be triggered to achieve remote code execution; bypassPermissions in .claude/settings.json can bypass permission checks to enable unrestricted tool execution; Grok Build CLI inherits Claude Code CLI’s permission configuration model, presenting similar risks; and .mcp.json introduces additional attack surface through MCP configuration. SlowMist noted that when AI coding agents over-trust project-level files, opening a project is essentially equivalent to granting shell access.