2026 Opening with Millions in Profit: 'God of War' Vida Reviews the Entire Trading Process of the BROCCOLI714 Incident

比推Publicado a 2026-01-01Actualizado a 2026-01-01

Resumen

In January 2026, crypto trader Vida profited over $1 million during the BROCCOLI714 incident, which involved a suspected hacked market maker account on Binance. Vida’s pre-existing $200,000 long position in BROCCOLI714 and a $500,000 funding rate arbitrage position were already in place. Alert systems triggered when the token’s price surged abnormally and a massive spot-contract price gap emerged. Recognizing the order book showed a highly unusual $26 million in buy orders—indicating a hack or system error rather than legitimate market activity—Vida quickly closed his arbitrage positions for a $300,000 gain. He then capitalized on the volatility by adding long positions in Binance perpetual contracts during a brief “reduce-only” lift and later selling his holdings for $1.5 million as signs of the attacker’s withdrawal emerged. Anticipating a crash once Binance risk controls intervened, Vida opened $400,000 in short positions around $0.065 and closed near $0.02, further boosting profits. Key factors included his automated alert systems, real-time order book analysis, collaboration with other traders, and correctly predicting the attacker’s exit strategy.

Vida : Born after 2000, founder of Equation News, skilled in program trading. He has shared stories of making tens of millions of dollars in the crypto market.

Preliminary Context: At 01:23 AM Beijing Time on January 1, 2026, Equation News monitored: A market maker's Binance account was highly suspected to be compromised. The potential attacker was疑似 using approximately $10 million to $20 million from the account to集中 pump the price of the BROCCOLI714-USDT trading pair on the Binance spot market.

Below is the full text by Vida:

《Review: Making $1 Million in the Recent BROCCOLI714 Hack Incident》

Preconditions and Infrastructure:

- I had a long-term accumulated position of $200,000 in BROCCOLI714 at a cost of 0.016, purchased around early November this year. It included both spot and contract holdings. After buying, I was trapped and too afraid to even look at it.

- The market maker's manipulation style in October-November was to rapidly pump the price within a few hours and then immediately dump with a large bearish candle. So, I set up an alert for my small-cap holdings that would wake me up if the price increased by over 30% within 1800 seconds.

- I also had a Binance perpetual contract funding rate arbitrage position for BROCCOLI714USDT with an average entry price of around 0.015 and a size of $500,000.

When the huge spot-contract price disparity occurred: My short-term surge alert program and my spot-contract spread alert program were both疯狂 alarming > prompting me to focus fully and rush to my computer to start working.

I第一时间 mentioned this situation in a core Chinese group on带带:

- My first reaction was to quickly close my funding rate arbitrage position. Because my original $500,000 arbitrage hedge position had become $800,000 in spot value and $500,000 in contracts. I immediately closed all arbitrage positions to lock in a profit of $300,000.

– But upon second thought, it felt very反常 because historically, no market maker would pump the spot market so violently regardless of the spread. I took a look at the order book depth and was震惊 to find that the bid-side 10% depth on Binance spot had $5 million in buy orders, while the contract side's bid 10% depth was only $50,000. Someone suggested a suspected Binance account hack, which I also found reasonable.

– I looked at the order book on the Binance main site again and was shocked to find that for BROCCOLI714, a coin with a market cap of $40m at the time, there were $26 million in bid orders. From this, I inferred that it must be either a hacked account or a market maker program bug, because no market maker would be foolish enough to play charity like this in the spot market.

- Seeing that the hacker had $26 million in ammunition on the spot order book, I knew his goal was to pump the spot market > lift the contract price > exit his position on the contracts.

So I monitored the changes in Binance's order book on one screen. I knew that as long as the hacker didn't withdraw the $20 million in buy orders on the spot market, the price of BROCCOLI714 would keep rising.

My first thought at this point was to go long on Binance contracts, but I found that the Binance contracts had already triggered the "circuit breaker protection mechanism" (reduce-only mode).

At that time, BROCCOLI spot was already at 0.07, while Binance contracts were capped at 0.038 by the circuit breaker mechanism, and Bybit contracts had risen to 0.055. So I chose to attempt a long position on the Binance BROCCOLI714USDT perpetual contract every 5-10 seconds on my trading terminal. If the order succeeded, it meant the circuit breaker period was over, meaning the Binance contract would pump.

I successfully蹲守到 this opportunity and added approximately $200,000 in long positions at a contract entry cost of 0.046.

- I knew this incident was必然 caused by a hacker or a market maker program bug, and the short-term surge was too high. The final outcome would inevitably be a complete mess.

So I kept watching the Binance spot order book.

The hacker withdrew his orders once midway, leading me to believe he had been sanctioned by Binance's risk control department. So, at Beijing Time 2026-01-01 04:20:52.732, I started using my trading program to疯狂 sell > liquidate all my previously held + later added long BROCCOLI714 spot and contract positions regardless of cost.

My original $200,000 accumulated position + the later added $200,000 roughly cashed out to $1.5 million. (A lot of the original accumulated position was opened in the contract market, so I didn't capture as much premium)

After being scared off by the hacker's withdrawal of buy orders at 4:21, the不讲武德 hacker挂回 the buy orders about 1 minute later and directly pumped the price to 0.15.

But I knew he would eventually be sanctioned by Binance's risk control department. And once his account was risk-controlled > bids withdrawn > broccoli would crash, it was just that the staff might be lazy at 1.1 AM so he hadn't been risk-controlled yet.

So I kept a close eye on the order book.

Later, at 4:31, I noticed the hacker really withdrew all the bids. At 4:32, they were completely withdrawn. And this time, they didn't reappear for a long time + group friends said someone probably contacted Binance tech, and he was likely sanctioned.

So I started shorting. I opened roughly $400,000 in short positions on Binance contracts at an average cost of around 0.065. The final closing price was approximately 0.02.

Revisiting why I was able to seize this opportunity:

1. Price anomaly alerts for small-cap strategies
- I set up short-term price surge alerts for small-cap strategies. As long as a held small-cap coin experiences an ultra-large price increase in a short time, it triggers a mandatory alert, 100% guaranteed to wake me up. – In the funding rate arbitrage strategy, I also set up monitoring: once a huge spread between spot and contract is detected, it triggers a mandatory alert.

2. Identifying反常 price action and verifying the order book
When I saw clearly反常 price action, the first thing I did was look at the order book to judge how much ammunition the "market maker" actually had. The result: For a coin with only a $30 million market cap, there were $20 million USDT in bids on the Binance spot side. From this, I judged this couldn't be normal market maker manipulation, but more like hacker behavior or a market maker's system bug (no market maker would pump the spot so recklessly and foolishly regardless of cost).

3. Still need to communicate more with experts. Brainstorming among several experts often helps figure out the entire剧本玩法 in the first moment.

4. I was very clear about the second phase玩法:
Wait for the hacker to be sanctioned by Binance's risk control department and withdraw the bid orders, then蹲守 this opportunity to short. So after completing the first phase of selling, I kept staring at the order book, waiting for this opportunity to appear. I waited over ten minutes and really managed to蹲守到 it.

One behavior made me guess the BROCCOLI714 hacker was probably wrapping up, because at Beijing Time 4:28:15, he不计成本 bought SOLUSDT spot, pumping it by about 5% >>> which triggered my pre-set alert again, letting me know.

I guessed that his account might have been partially restricted by Binance from placing new orders in the BROCCOLI714 market, so he狗急跳墙 and bought SOL instead.

结果真的 (Sure enough), 3 minutes later the BROCCOLI price collapsed.


Twitter:https://twitter.com/BitpushNewsCN

Bitpush TG Discussion Group:https://t.me/BitPushCommunity

Bitpush TG Subscription: https://t.me/bitpush

Original article link:https://www.bitpush.news/articles/7599510

Preguntas relacionadas

QWhat was the initial position and cost basis of Vida's long-term BROCCOLI714 holdings?

AVida had a long-term BROCCOLI714 position with a cost basis of $0.016, totaling $200,000, which was accumulated in early November.

QWhat two types of alerts did Vida have set up that helped him detect the unusual market activity?

AHe had two alerts: one for a price increase of over 30% within 1800 seconds for his small-cap holdings, and another for a significant spot-contract price difference in his funding rate arbitrage strategy.

QWhat observation in the order book led Vida to conclude this was not normal market maker activity but likely a hack or bug?

AHe observed that for a coin with a market cap of around $40 million, there was an unusually large bid of $26 million USDT on the Binance spot order book, which no rational market maker would place.

QWhy did Vida decide to short BROCCOLI714 after initially selling his long positions?

AHe anticipated that the hacker's buy orders would eventually be withdrawn after being sanctioned by Binance's risk control department, causing the price to crash, which would create an opportunity to profit from a short position.

QWhat final clue suggested to Vida that the hacker was being restricted and that the BROCCOLI714 price was about to collapse?

AThe hacker made an irrational large purchase of SOLUSDT, spiking its price by 5%, which Vida interpreted as the hacker being blocked from trading BROCCOLI714 and acting out of desperation. The price of BROCCOLI714 collapsed shortly after.

Lecturas Relacionadas

The Essence of AI Layoffs: Why More AI Adoption Leads to More Corporate Anxiety?

The author, awaiting potential inclusion on an 8000-person layoff list, analyzes the true nature of recent "AI-driven" layoffs. They argue that while AI use, particularly tools like Claude for code generation, has skyrocketed and boosted developer output (e.g., 2-5x more code commits), this has not translated into proportional business growth or revenue. The core issue is a misalignment between increased "Input" (code) and tangible "Outcomes" (user value, revenue). AI acts as a costly B2B SaaS, inflating operational expenses without guaranteed returns. Two key problems emerge: 1) The friction that once filtered out bad ideas is gone, as AI allows cheap pursuit of even weak concepts. 2) Organizational "alignment tax"—the difficulty of coordinating across teams—becomes crippling when development velocity outpaces consensus-building. Thus, layoffs serve two immediate purposes: 1) To offset ballooning AI costs (Token consumption) and maintain cash flow, as rising input costs without outcome growth destroys unit economics. 2) To reduce organizational bloat and alignment friction by simply removing teams, thereby speeding up execution in the short term. Therefore, these layoffs are fundamentally caused by AI, even if AI doesn't directly replace roles. They represent a painful correction until companies learn to convert AI-driven productivity into real business outcomes and streamline organizational coordination to match the new pace of work. The cycle will continue until this learning curve is mastered.

marsbitHace 7 min(s)

The Essence of AI Layoffs: Why More AI Adoption Leads to More Corporate Anxiety?

marsbitHace 7 min(s)

Can the Solana Foundation and Google's Collaboration on Pay.sh Bridge the Payment Link Between Web2 and Web3 in the Agent Economy?

Solana Foundation, in collaboration with Google Cloud, has launched Pay.sh, a payment gateway designed to bridge the gap between AI agents and enterprise-grade service infrastructure. The initiative aims to solve a key bottleneck in the "agent economy": existing payment systems are ill-suited for autonomous AI agents. Traditional methods like credit cards require human verification, while newer on-chain protocols like x402 and MPP create a separate, Web3-native system that raises barriers for service providers. Pay.sh functions as a universal payment layer. It allows users to fund a Solana wallet via credit card or stablecoin, which then acts as an identity and payment proxy for AI agents. When an agent needs to access a paid API service (e.g., Google Cloud, Alibaba Cloud), Pay.sh handles the transaction seamlessly. It leverages the HTTP 402 status code ("Payment Required") to initiate payments, intelligently choosing between one-time transfers (x402-style) or session-based authorizations (MPC-style) based on the service's billing model. This spares agents from manual account registration and API key management. A key feature for service providers is low integration effort. They can adopt Pay.sh by providing a declarative configuration file, enabling features like tiered pricing, free tiers, and automatic revenue splitting to multiple addresses (e.g., for royalties, cloud costs). Providers can also list their APIs in a central Pay Skill Registry for agent discovery. The collaboration with Google Cloud provides crucial infrastructure for API proxying, traffic routing, and compliance logging, aiming to keep agent activities within regulated boundaries. By connecting Web2 services with Web3 payment rails, Pay.sh positions the Solana wallet as a foundational identity and payment tool for AI agents, potentially driving more transaction volume to the Solana ecosystem. However, the report notes challenges. The service registry currently lacks robust vetting, risking exposure to unauthorized or malicious third-party APIs. Pay.sh also inherits security and compatibility risks from its underlying payment protocols (x402, MPC). Furthermore, adoption may be hindered by varying regional data privacy and payment compliance regulations among API providers. Despite these hurdles, Pay.sh represents a significant step towards integrating Web2 and Web3 for autonomous agent commerce.

marsbitHace 14 min(s)

Can the Solana Foundation and Google's Collaboration on Pay.sh Bridge the Payment Link Between Web2 and Web3 in the Agent Economy?

marsbitHace 14 min(s)

Bitcoin's Bull-Bear Cycle Indicator Turns Positive for the First Time in 7 Months: End of Bear Market or False Breakout?

Bitcoin's "Bull-Bear Market Cycle Indicator" from CryptoQuant has turned positive for the first time since October 2025. This gauge, based on the P&L Index relative to its 365-day moving average, suggests a potential shift from a bear market phase. Concurrently, the Bull Score Index rose to a neutral reading of 50 in late April. The indicator's move into positive territory follows a roughly 35% price rebound from a low near $60,000 in February to above $81,000. The recovery over approximately three months was faster than the 12-month period observed during the 2022 bear market. However, analysts caution against premature optimism, citing a historical precedent from March 2022. Back then, the Bull Score Index briefly hit 50, but it proved to be a false signal as Bitcoin's price subsequently plunged further. Structural differences exist in the current cycle, including consistent inflows into spot Bitcoin ETFs and an increase in large holder addresses. Yet, some models, referencing the four-year halving cycle, suggest a potential deeper bottom near $50,000 might still be possible around late 2026. In summary, while on-chain data shows marked improvement and the worst panic may be over, market participants remain cautious. A convincing trend reversal confirmation likely requires Bitcoin to sustainably break above key resistance, such as the 200-day moving average near $82,000.

marsbitHace 21 min(s)

Bitcoin's Bull-Bear Cycle Indicator Turns Positive for the First Time in 7 Months: End of Bear Market or False Breakout?

marsbitHace 21 min(s)

How to Automate Any Workflow with Claude Skills (Complete Tutorial)

This is a comprehensive guide to mastering Claude Skills, a feature for creating permanent, reusable instruction sets that automate specific workflows. Unlike simple saved prompts, Skills function like trained employees, delivering consistent, high-quality outputs by defining the entire task process, standards, error handling, and output format. The guide is structured in four phases: **Phase 1: Installation (5 minutes).** Skills are folders containing a `SKILL.md` file. The user is instructed to find a relevant Skill online, install it, test it on a real task, and compare its performance to one-off prompts. **Phase 2: Building Your First Custom Skill.** Start by rigorously defining the Skill's purpose, trigger phrases, and providing a concrete example of perfect output. The `SKILL.md` file has two parts: a YAML frontmatter with a specific name/description/triggers, and a detailed, step-by-step workflow written in natural language with examples and quality standards. **Phase 3: Testing & Optimization for Production.** Test the Skill in three scenarios: 1) a standard, common task; 2) edge cases with missing or conflicting data; and 3) a pressure test with maximum complexity. Any failure indicates a needed instruction. Implement a weekly optimization cycle to continuously refine the Skill based on real usage. **Phase 4: Building a Complete Skill Library.** The goal is to create a team of Skills for all repetitive tasks. Examples are given for industries like real estate, marketing, finance, consulting, and e-commerce. The user should list their tasks, prioritize them, and build one new Skill per week, maintaining a master document to track their library. The conclusion emphasizes the compounding time savings: ten Skills saving 30 minutes each per week reclaims over 260 hours (6.5 work weeks) per year, fundamentally transforming one's work system.

marsbitHace 45 min(s)

How to Automate Any Workflow with Claude Skills (Complete Tutorial)

marsbitHace 45 min(s)

Trading

Spot
Futuros
活动图片