If you tried to start a free phone trial since late October, apart from one short reopening, you hit a wall. That was on purpose, and I owe you an explanation. Some of you also saw the site go into maintenance in the middle of the day; I’ll come back to that below.
In a nutshell: a bug doesn’t explain it all. A small group of people treated our free trial as an unlimited supply of Canadian phone numbers, and a limit I had planned to deal with later made that costly for everyone else. Let’s take a few minutes: I’ll walk you through what happened, what I did, and what changes with version 0.14.0.
If you only have a minute
- When trials return, I plan to ask you to confirm your personal number by replying to our text from your mobile, or by answering our call on your landline.
- Our Terms of Service now clearly prohibit trial abuse. Every suspension for trial abuse is a decision I make myself, and you can appeal.
- I’m building a way to serve many more lines with the same capacity at our provider. That work isn’t finished yet.
- Once version 0.14.0 is approved by the App Store and Google Play, the mobile app will ask you to update before continuing.
What happened
On October 25, new accounts started arriving in large numbers. A few were even created in the same second.
The pattern kept repeating. From October 25 to 27, most accounts that took a trial did so less than a minute and a half after signing up. Then many of their trial numbers received one or two short texts but almost never sent any.
Think of the codes you get by text when you create an account on a website: short messages, each from a different service, that nobody replies to. Our trial numbers looked like the ones used to receive that kind of code. A Canadian number that can receive them for the whole length of a trial is worth something to someone creating accounts in bulk elsewhere. Our free trial was handing them out.
In eight days, from October 25 to November 1, 508 new accounts were created. Not all of them were part of this scheme, but 122 claimed a trial within minutes of signing up, or with a number we had already flagged as suspicious. Among their trial numbers, 26 received texts from several different senders.
What I looked at
You may be wondering what I looked at to get there. Here’s the precise answer. I used only activity data our systems record: when accounts signed up and claimed trials, how many texts each number received, how long they were, how many senders there were, and whether anything was sent.
To count senders, I used a scrambled version of each number, which shows whether two texts came from the same sender without showing the number. Our servers see the sender’s number to deliver a text, but this investigation didn’t need it. I also checked, in a targeted way, our servers’ technical logs, which record, among other things, which pages are requested, when, and from which IP address, a device’s internet address.
The content of texts isn’t part of this data. On our default storage path, it’s sealed after delivery and checks, with keys WIGGWIGG doesn’t hold; our Privacy Statement describes the exceptions.
Then it spread
A YouTube video, whose title promised free fake WhatsApp numbers and verification codes for every app, showed step by step how to get through our verification with a temporary number borrowed from a public website that receives texts for anyone. It also showed how to clear the app’s data to open more accounts and claim more trials, then let other people use trial numbers to receive their codes. People also showed me private Telegram groups selling the method, payable in cryptocurrency.
Several of you saw the video before I did and wrote to me on social media to warn me. Thank you: those messages really helped.
The person behind the video had first written to me on October 26 to offer a paid promotion. I didn’t answer. On November 1, they sent me the link to their video and asked me for numbers in bulk to hand out themselves. I said no and asked them to take the video down, citing our Responsible Use policy and our Terms of Service. They took it down that same day.
Why this hurt more than it might seem
Every phone line uses a “connection” at Telnyx, our telecom provider. That’s what lets the WIGGWIGG app make and receive calls over the internet with your number, including 911 calls from the app.
Our Telnyx account has a fixed limit of 100 connections. I knew about that limit, and I knew there was another way to work with it: having several lines share connections. My plan was to build that as WIGGWIGG grew.
Two things upended that plan. Because of a bug, our lines didn’t give their connection back when they were released, and the trial abuse filled the rest. We first hit the limit on October 25, the day the abuse started. On October 29, all 100 connections were in use. I asked Telnyx to raise the limit, and they pointed me back to that other way.
At the limit, a new line, even a paid one, could still be activated, but without calling in the app and without 911 in the app. The people exploiting the trial did not care: they only wanted to receive texts. For someone paying for their line, though, it changes everything. Protecting those people came first, and fortunately, no paying customer ended up in that situation.
What I did
Here are those two weeks at a glance, before the details.
The two weeks at a glance
The abuse What I did Maintenance Security
- Oct 21Security: Node.js, which runs our code, releases security fixes
- Oct 22Security: That evening, our servers move to the fixed version
- Oct 25The abuse: The abuse starts and the connection limit is reached
- Oct 26What I did: Released lines finally give their connection back
- Oct 27What I did: New trials paused
- Oct 27Maintenance: Two maintenance windows in the middle of the day
- Oct 29The abuse: All 100 connections are in use
- Oct 30What I did: 19 accounts suspended and their lines released
- Oct 30Maintenance: Two maintenance windows
- Oct 31What I did: Trials reopen with a verified personal number
- Nov 1The abuse: I learn about a video showing the bypass
- Nov 1The abuse: 63 trials claimed in just over 9 hours
- Nov 1What I did: Trials paused again and Terms updated
- Nov 1What I did: 82 more accounts suspended
- Nov 1What I did: Video taken down at my request
- Nov 3 and 5Maintenance: Two more maintenance windows
- Nov 8What I did: Our lines use only 60 connections
- I paused new trials. On October 27, I stopped new trial activations. Existing lines kept working.
- I required a verified personal number. On October 31, trials reopened with a new step: verify a Canadian personal number, mobile or landline, with a code sent by text or by call. Internet-based and toll-free numbers are refused, as is a number whose line type cannot be confirmed. A number can be used by only one account at a time.
- I watched that step get bypassed. That’s the method the video showed. By the morning of November 1, 63 trials had been claimed in just over nine hours, almost as many as in the first three days of the abuse. I paused trials again that morning.
- I suspended abusive accounts, with a right to appeal. On October 30, I suspended a first group of 19 accounts and released their lines. On November 1, I updated our Terms of Service to clearly prohibit abusing the free trial, then suspended 82 more accounts. All 101 of these suspensions came from me, not from an automated system. None of these accounts was a paying customer, and as of November 8, none had appealed.
- I took connections back. The suspensions also served that purpose: getting those accounts’ connections back without waiting for their trials to end, so there would be some left for people buying a line or starting a trial in good faith. It took a change to the system on November 1 for their lines to actually give their connection back. Released lines, which used to keep their connection, now give it back. Trial lines that forward their calls and have never used calling, in the app or on the web, give theirs back too after three days; they get ready again the first time you open calling in the app.
- I started building shared connections, sooner than planned. This is the other way I mentioned. Instead of every line needing its own connection, up to 10 lines will share one group under the planned settings, and that group will use 2 connections for ordinary calls. A problem with one group’s connection or spending limit will affect only that group. This work is still in progress; once it’s done, I’ll turn the groups on gradually.
The result, as of November 8: none of the suspended accounts’ 100 lines still held a connection, 102 lines had given theirs back, and our lines were using only 60.
If your account is suspended
Building a way to suspend accounts also meant building a way out. If your account is suspended:
- you see the reason and how long the suspension lasts;
- you can appeal and reach support;
- 911 stays available while you keep your number;
- your numbers are held for at least 10 days, and for as long as an appeal is open;
- your paid plans stop renewing, and no new charges start while the suspension lasts. If it is lifted, the suspended days are added to your current period.
These safeguards arrived along the way. The first group, suspended on October 30, had their lines released right away, and the notices they received may not have given a reason. Since November 1, a suspended account’s numbers are held for at least 10 days instead of being released right away, and with version 0.14.0, a suspension notice gives the reason and how long it lasts.
What changes when trials come back
When trials reopen, here’s how I plan to have you confirm your personal number:
| Your number | How you confirm it |
|---|---|
| A mobile | You reply to our text, from that same number, with the code it contains |
| A landline | You answer our call and enter the code |
The reply is what makes the difference: a website that receives texts for anyone can’t send one back. You need a number that can send texts, and on a prepaid plan your carrier may charge you for that text. Each step has its own switch, so I can adjust quickly depending on what I see.
If what you need to start a trial ever changes, the trial page will say so before you begin.
As for the trial itself: when it reopens, it will last 14 days, include 100 units, and never turn into a paid plan on its own. Trials won’t reopen before the new app version is available in the App Store and on Google Play and our updated Privacy Statement is in effect. They’ll reopen gradually, and I can limit or stop new activations at any time.
Maintenance in the middle of the day
Several of the fixes against the abuse had to go live quickly, at a time when most of you are using WIGGWIGG. That meant six maintenance windows in the middle of the day, each lasting from 10 minutes to almost an hour, between October 27 and November 5. Waiting for the evening would have delayed those fixes by a few hours. I chose not to wait. I’m sorry for those interruptions.
Meanwhile, a wave of security fixes
As if that weren’t enough, the whole web was patching this fall. AI tools are now helping find security holes in the software everyone builds on, and the fixes are arriving in waves:
- PHP, a programming language that by some estimates runs nearly 70% of websites, disclosed critical flaws in October that were found with the help of AI models (CNBC). We don’t use PHP, but the same wave reached software we do use.
- Node.js, the environment our web app and server code runs in, fixed 10 vulnerabilities on October 21. One of the four high-severity ones was reported by an AI security tool (Node.js advisory).
- nginx, widely used software that receives a website’s visitors and sits in front of our forum, the Community, and the tool that schedules our social media posts, lists 26 vulnerabilities with 2026 identifiers, compared with 2 with 2025 identifiers (nginx).
- IBM X-Force, IBM’s security research team, counted nearly seven times as many disclosed vulnerabilities at four major software makers in the first nine months of 2026 as in the same period of 2025. It says AI-assisted research may be contributing (IBM X-Force).
For a small company, that means patching often and quickly. Here is what it looked like for us.
Our web app and its servers were running the fixed version of Node.js by the night of October 22 to 23, less than two days after its release and just before the trial abuse started. A daily check now spots an outdated Node.js version, and our deployment tool refuses to ship it.
Around the same time, scans found known flaws in ready-made software from other projects that we run behind the scenes: our customer relationship tool, our monitoring tool, and the tool that schedules our social media posts. None of them is the WIGGWIGG app or website you use. Our monitoring tool does receive technical data from our servers, reachable only behind our administrator sign-in. Here is what I did:
- our customer relationship tool runs in a restricted mode, with no outgoing email and no real contacts, until a fixed version is available;
- for the monitoring and social media tools, I pinned the exact versions we run, scanned them, and froze changes while verified replacements with no known flaws are prepared;
- the few exceptions accepted in the meantime end on November 17;
- the scan of our packaged software before each release now counts as a failure if it can’t run;
- the check of the software libraries we ship against known flaws is now stricter.
None of this shows in the app, but it took its share of my days.
Version 0.14.0 and the mobile app
Version 0.14.0 is a big release: more than 200 changes, about a hundred of which affect you directly. The rest happens behind the scenes. The summary of version 0.14.0 covers the highlights, and the release notes for version 0.14.0 describe each of the changes that affect you.
Version 0.14.0 arrives in two stages: first on the web, then in the mobile app. Once the mobile app is approved by the App Store and Google Play, it will ask you to update from version 0.13 to version 0.14 before continuing. The new trial verification needs it. Store approval can take a few days. I’ll update this post as soon as the required update is in place.
WIGGWIGG is built by one person. Trial abuse, a provider limit, and a wave of security fixes, all in the same two weeks: that was a lot to handle at once, and the timing couldn’t have been worse. But we got there, and the service is much more stable now.
If anything here affects you directly, contact us: I read everything. And thank you, sincerely, to everyone who took the time to warn me.
CAB is the founder of WIGGWIGG, a privacy-first digital identity platform built in Quebec, Canada.