WeWorm: AI built a zero-click WeChat exploit in 2 days
Researchers used AI to find a WeChat VoIP memory bug and weaponize it in about two days. Exploit development just got faster than your patch cycle.
Security firm Calif built a zero-click worm for WeChat — an app with over a billion users — and the headline is not the worm. It is the clock. The team found a memory-corruption bug in WeChat's VoIP stack and had working remote code execution in roughly two days, with the self-propagating worm about a week later. AI did the heavy lifting on both the bug hunt and the initial exploit. That is the number every operator should be writing down.
What actually happened
The flaw sits in WeChat's voice-call handling. An incoming call from an attacker triggers memory corruption before the victim does anything — no tap, no answer. Help Net Security reports that the account is taken over while the phone is still ringing, and the code then reads the victim's contacts and calls them. Compromise to re-propagation, in seconds, with no human in the loop.
Calif reported it privately to Tencent, which shipped patched iOS and Android builds plus a server-side mitigation that protects users with no action on their part. Researchers withheld technical details and found no evidence of real-world abuse before the fix. Experts quoted in the coverage estimated the worm could have reached hundreds of millions of devices within hours if it had been released.
We are not naming a CVE here, because none was published in the reporting we could verify.
Why AI-accelerated exploit development matters for your business
You do not run WeChat's VoIP stack. You do run something with a parser in it — an image handler, a webhook receiver, a PDF pipeline, a media upload path. The transferable fact is that a small team compressed "find a memory bug in a hardened billion-user app" and "write working RCE" into about two days by pointing models at it.
Every patch-window assumption you have is priced off the old cost of exploit development. That price just fell. Two consequences:
- Time-to-exploit is collapsing, so time-to-patch has to. We wrote about the Adobe Commerce store that fell 50 minutes after the exploitation report. That is the shape of the new window. A monthly patch cadence is now a policy that describes last decade.
- Zero-click means user training does nothing. No amount of "don't click suspicious links" defends an account that is taken over mid-ring. Controls have to be structural: keep untrusted input away from native parsers, sandbox the ones you cannot avoid, and be able to revoke sessions and tokens fast when something lands.
The optimistic read is real, too. The same acceleration is available to defenders — the researchers here were the good guys, and Tencent's users were protected before anyone knew. But attackers get the tool on the same day you do, and they do not have a change advisory board.
Key takeaways
- Calif used AI to find a WeChat VoIP memory-corruption bug and build working RCE in about two days; the worm took roughly another week
- WeWorm is zero-click — the account is compromised while the phone rings, then spreads itself through the victim's contacts
- Tencent patched iOS and Android and added a server-side mitigation; no in-the-wild abuse was found and no CVE was published in the coverage we verified
- The operator lesson is the timeline, not the app: exploit development is getting cheaper, so patch windows must shrink to match
- Zero-click attacks make user training irrelevant — put the controls in the architecture and in your ability to revoke access fast
Still patching on a monthly cadence? We build systems where shipping a security fix is a same-day, low-drama event — because the deploy path was designed for it. See how we build or talk through your patch window.
Sources: Help Net Security, Security Affairs.
- #ai-security
- #zero-click
- #exploit-development
- #patch-management
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Telerik RadAsyncUpload RCE: hardening is the precondition
A public exploit turns four Telerik UI for ASP.NET AJAX bugs into unauthenticated RCE — and the 2017 hardening step everyone was told to apply is what makes it work.
Read itSAP CVSS 10.0: an unauthenticated crash in Web Dispatcher
SAP's September Patch Day fixes CVE-2026-44756, a CVSS 10.0 memory corruption bug in Extended Passport processing that reaches Kernel and Web Dispatcher unauthenticated.
Read it