Father Loses Job Over Son’s $118K YouTube Ad Bill [2026] – tech-insider.org

A father says his 9-year-old son spent $118,000 on YouTube ad campaigns promoting the boy’s Minecraft and Roblox gaming videos, all charged to a company credit card saved in the father’s Google account. The father, identified by IBTimes UK as David “Dave” Sarkisyan, says he was fired after his employer’s finance team traced three weeks of unexplained advertising charges back to his son’s YouTube channel, Mighty Mike Plays. The company is now demanding the full $118,000 back within 30 days, according to multiple outlets that have picked up the story since Tom’s Hardware first reported it on September 16, 2026.
The story has since traveled through outlets including Gadget Review, Moneycontrol, American Bazaar, Yahoo, Gigazine in Japan, iXBT.games, VGC, and Vision Times, each repeating the same core numbers while flagging the same caveat: the account comes from the father himself, and as Moneycontrol noted, it “has not been independently verified,” a line Vision Times echoed in its own September 2026 writeup on the story. VGC’s September 2026 coverage separately confirmed the boy’s age as 9. No statement from Google or YouTube has surfaced in any of the coverage. What’s clear is that a story about a 9-year-old, a saved payment method, and a six-figure ad bill has become one of the most discussed hardware and gaming stories of the week, and it raises real questions about how corporate credit cards, family Google accounts, and self-serve ad platforms interact when nobody is watching the meter.
Industry insights, the latest tech news, and special interviews, all in the Tech Insider Newsletter.

One email a week. No spam, unsubscribe anytime.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
According to Tom’s Hardware, Dave’s son runs a YouTube channel under the handle MightyMikePlays67, where he posts Minecraft and Roblox gameplay videos, a detail GamesRadar+ independently confirmed in its own September 2026 coverage of the ad campaigns. At some point, Dave showed his son how to promote one of those videos with a small YouTube ad campaign, which Moneycontrol’s September 2026 reporting specifically pegged at $20. That single lesson was the extent of what Dave intended. Over roughly three weeks that followed, his son kept going on his own, setting up additional ad campaigns without telling his father, all billed to the same saved company credit card. IBTimes UK reports the final total came to $118,479.83, or about £88,493.73 at current exchange rates, a figure that lines up closely with the $118,000 headline number used across nearly every outlet covering the story.
The mechanism, as described in the reporting, was straightforward and unremarkable right up until it wasn’t. Dave’s business card was saved to a Google account that his son also had access to, which meant creating and funding a new YouTube ad campaign required no new card entry and no extra confirmation beyond clicking through the campaign setup. Gadget Review, citing Tom’s Hardware, quoted the boy’s own explanation for why he kept going: “The credit card, it just says approved every single time.” That line captures the entire failure mode in a single sentence. There was no spending cap, no alert threshold, and no friction between a child’s curiosity and a payment method tied to a real employer.
Running a YouTube ad campaign does not require a business account, an agency login, or any credential a typical adult would consider “professional.” Google’s self-serve ad tools let anyone with an active Google account and a payment method attach a campaign to a YouTube video within a few clicks, a design built for small creators and local businesses to promote content cheaply, documented in Google’s own Ads support documentation. That same low-friction design is what let a 9-year-old repeat the process dozens of times over three weeks without hitting a wall that would stop an adult acting in bad faith, let alone a child who had no idea the numbers were real money.
Finance later showed Dave a breakdown of three weeks of ad spend tied to campaigns with names like “Mighty Mike,” “Epic Roblox,” and straightforward Minecraft gameplay promotions, according to both Tom’s Hardware and Gadget Review’s reporting. Three of the promoted videos reportedly reached around 200,000 views combined, a figure TweakTown’s September 2026 coverage independently reported as well, meaning the campaigns weren’t sitting idle burning through budget with no delivery. They were actually serving, actually getting clicks, and actually running up real charges against a live advertising auction, the same auction any marketing team uses to buy YouTube inventory.
The reporting is consistent on the shape of the timeline even where exact calendar dates are missing. Dave taught his son how to run one modest video ad, in the $20 range. From there, the son built out more campaigns on his own, and the spending compounded over about three weeks before anyone at the company noticed. Discovery didn’t come from a banking alert or a card-lock trigger. It came the old-fashioned way: a finance department noticing a large, unexplained vendor charge during a routine review and pulling the employee into a meeting to explain it.
Spread evenly across three weeks, the confirmed $118,479.83 total works out to roughly $5,642 a day, or around $235 an hour if it had run continuously — though the real pattern was almost certainly uneven, clustering around whenever the son was active on a tablet or computer rather than arriving in a smooth drip. Google Ads campaigns bill per click or per thousand impressions, so a total that size over three weeks implies the campaigns were actually winning a meaningful number of ad auctions against other advertisers bidding for the same YouTube inventory, not simply sitting configured with an inflated budget nobody used.
Most corporate card programs still rely on a monthly statement cycle or a periodic manual review rather than live transaction monitoring, which is precisely the gap a three-week run of ad charges fell into. A single $20 campaign would never trip any fraud filter a bank or card issuer runs, since it looks exactly like legitimate small-business ad spend. The problem is that the same system that waves through a $20 charge has no mechanism for noticing that the account has now generated dozens of similar charges in a matter of weeks with no prior advertising history attached to it. That pattern, a brand-new account suddenly generating repeated same-day charges, is the kind of anomaly real-time monitoring tools are built to flag within hours, not weeks, which is exactly why this case is likely to become a reference point for vendors selling that capability.
Gadget Review’s account of the meeting is blunt: Dave “did not expect to walk into a conference room with his manager, corporate staff, and finance and learn that his 9-year-old son had reportedly spent $118,000 on YouTube ad campaigns.” NewsBreak’s version adds that he was shown a full breakdown of the advertising spend and asked to account for the total on the spot. For a company, a charge of that size on a corporate card sitting unexplained for three weeks is a serious internal-controls failure regardless of who ultimately benefited from the ad spend, which is likely why the response moved so fast to termination and a repayment demand rather than, say, a warning or a payment plan negotiated in that same meeting.
Companies rarely respond to a card anomaly with a quiet conversation once the number involved reaches six figures. Finance teams are trained to treat an unexplained charge as a potential fraud or embezzlement event until proven otherwise, which is why Dave’s meeting reportedly included his manager, corporate staff, and finance together rather than a single supervisor asking an informal question. Pulling in multiple departments at once also creates a documented record from the first conversation, something companies generally want in place before any termination or repayment demand, since a dispute later over whether someone was warned or given a chance to explain depends heavily on what got written down in that initial meeting. A charge spread across three weeks and landing at $118,479.83 is large enough that treating it any other way would itself look like a lapse in internal controls.
According to iXBT.games, Dave announced in a follow-up video that he had been fired and that his former employer is demanding the entire $118,000 back within 30 days. IBTimes UK reports that he and his wife have discussed selling their home to cover the bill, and that he has ruled out two of the most common financial-crisis playbooks people reach for in situations like this: he says he will not set up a GoFundMe campaign, and he will not launch a cryptocurrency token tied to the story to try to recoup the money, something that has become a recurring, controversial move among people who go viral for financial trouble. His own summary of the road ahead, as captured in the archived Tom’s Hardware headline, was blunt: “I’m going to be working until I’m like 94.”
That refusal is notable on its own. Coin launches tied to personal misfortune have become common enough in 2026 that declining one is now treated as a small news beat in itself. Dave’s stance, at least as reported, is that he intends to work the debt down the conventional way rather than try to monetize the viral attention the story has generated.
By October 2026, the job loss stopped resting solely on Dave’s own account. Dexerto reported plainly that Dave “has now lost his job,” and Yahoo’s October coverage went further, stating he “has lost his job as a result of the incident” rather than framing it as an unverified claim. That shift matters because nearly every detail in this story, the $118,000 figure, the three-week timeline, the firing itself, had previously traced back to Dave’s own retelling, repeated outlet after outlet with the same verification caveat Moneycontrol raised early on. Independent phrasing from Dexerto and Yahoo doesn’t mean Google or YouTube have confirmed anything. Neither company has issued a statement, and nothing in the reporting suggests they plan to. But it does mean two outlets outside the original reporting chain are now treating the firing as settled fact rather than a claim awaiting confirmation, a meaningfully different place for a story to sit several weeks after it first broke. Dexerto and iXBT.games report the repayment demand in the same direct terms, stating plainly that the former employer wants the full $118,000 back within 30 days, rather than attributing the demand only to Dave’s own account.
The spread of this story is worth tracking on its own, because the number of outlets independently repeating its core facts has grown steadily since Tom’s Hardware broke it on September 16, 2026. Yahoo Entertainment’s own September 2026 writeup independently confirmed the channel name, Mighty Mike Plays, that has since become shorthand for the whole case. What started as a single detailed account has, in the weeks since, moved through gaming press, financial media, and general-interest outlets on multiple continents, with each pickup adding a detail rather than simply reposting a summary.
The first wave followed quickly. Gadget Review and NewsBreak added detail on the finance-department meeting, Moneycontrol raised the verification caveat that would follow the story through nearly every later writeup, American Bazaar carried it for a South Asian readership, Gigazine picked it up in Japan, and iXBT.games reported the repayment figure for a Russian-language audience. Within a short span, the same $118,000 number was running in outlets based in the United States, India, Japan, and Russia, unusually broad distribution for a story that remains, at its core, one father’s account of his own son’s actions.
The second wave, landing in October 2026, is where the framing shifted from “a man says this happened” toward something closer to accepted fact. Dexerto’s coverage states outright that Dave has lost his job, rather than that he claims to have. Yahoo’s October writeup uses similarly direct language, describing the job loss as something that happened “as a result of the incident.” The Register, a publication that typically covers enterprise technology and corporate IT policy rather than gaming or viral content, independently reported that the ad spending ran for three weeks, the same window established in the original reporting, which cross-checks the earlier timeline rather than revising it. IBTimes UK’s more precise $118,479.83 figure has also held up across every outlet that cites an exact number instead of rounding to $118,000.
What hasn’t changed across either wave of coverage is the absence of any Google or YouTube statement. Every outlet involved, from Tom’s Hardware in September to Dexerto and The Register in October, is still working from Dave’s account, employer documentation he has described but not published, and each other’s reporting. What’s different by October is that the firing and the repayment demand now appear in multiple outlets’ own declarative language rather than attributed solely to Dave, even though the underlying ad-spend total and the three-week mechanism remain exactly as originally reported. For a story with no official confirmation from the platform at its center, that kind of cross-outlet convergence is about as close to verification as this case is likely to get.
Break the repayment demand down to a daily figure and the pressure gets easier to picture: $118,479.83 collected over 30 days works out to roughly $3,949 a day, a faster clock than the $5,642-a-day pace at which the money actually disappeared over three weeks. The company wants the debt erased almost as quickly as a 9-year-old spent it, except Dave doesn’t have an ad auction working in his favor on the way back, just a deadline.
Few households keep six figures sitting in liquid savings, which narrows the realistic options to a short list: draining retirement accounts, which typically triggers taxes and early-withdrawal penalties on top of the loss; taking out a personal loan or a home-equity line of credit against whatever equity the family has built; negotiating a structured payment plan directly with the former employer; or selling the house outright, the option IBTimes UK reports Dave and his wife are actively discussing. The problem with that last option as a 30-day fix is timing. A home sale, from listing to a closed transaction with funds actually in hand, typically takes weeks to months even in a fast-moving market, not the single month the company has given him. If selling the house is genuinely the plan, the timeline alone makes it almost impossible to land before the stated deadline passes.
That mismatch between a 30-day demand and a multi-month asset sale is very likely why companies in situations like this tend to treat a hard repayment deadline as an opening position in a negotiation rather than a figure they genuinely expect to collect in full and on schedule, especially once it’s clear the borrower’s only large asset is a primary residence that can’t be converted to cash on command.
The single point of failure in this story isn’t a hack, a phishing email, or a data breach. It’s a saved payment method sitting inside a shared or accessible Google account. Business credit cards get saved to personal Google accounts constantly, for legitimate reasons: buying software subscriptions, expensing small purchases, running a side project. The problem is that once a card is saved, Google’s ad tools treat “has the account open” as sufficient authorization to spend against it, with no secondary confirmation step scaled to the size of the charge. A $20 test ad and a $20,000 campaign go through the identical click path.
Family tech researchers have flagged this exact gap for years: platforms build spending guardrails for known “kids’ apps” and app-store purchases, but self-serve advertising tools were designed for small businesses and creators, not built with a child-safety threat model in mind at all. Nobody expected a 9-year-old to be the one operating them. The same pattern shows up in how consoles handle parental spending controls, where guardrails vary widely by platform and rarely extend to third-party tools like a browser-based ad dashboard.
The guardrails that do exist across the tech industry overwhelmingly sit on the consumer side of the business. App stores added purchase-confirmation prompts and parental PIN requirements after years of headlines about kids racking up charges in mobile games. Streaming and console platforms added spending limits tied to family accounts for the same reason. Advertising dashboards never went through that same pressure because the entire product category was built for marketers, freelancers, and small-business owners, a user base nobody designing the onboarding flow pictured as including a 9-year-old. That gap is exactly why a child could move through campaign creation, billing, and launch without ever hitting a prompt designed to ask, in effect, whether a human who understands money is actually the one clicking the button.
The regulatory framework most people assume governs kids and online platforms doesn’t actually reach what happened in this case. The Children’s Online Privacy Protection Act, enforced by the Federal Trade Commission, governs how platforms collect and use personal data from children under 13. It has nothing to do with who is permitted to spend money through a platform’s advertising tools. YouTube’s method of complying with COPPA is its “Made for Kids” designation, which creators apply either themselves or through YouTube’s own audience-detection system. Content flagged that way has personalized advertising switched off and comments, notifications, and several other features restricted, specifically to limit how much data gets collected from child viewers watching a video, not to limit who can buy ads promoting it.
None of that machinery was built to ask who sits on the buying side of a campaign rather than the viewing side. Dave’s son wasn’t a child YouTube needed to shield from targeted advertising; he was a child who opened Google Ads and became an advertiser in his own right, bidding into the same auction any marketing department uses. COPPA and the “Made for Kids” label built on top of it regulate the viewer half of the platform. The buyer half, the self-serve dashboard that let a 9-year-old commit $118,479.83 of a company’s money to live ad campaigns, sits entirely outside that structure, because the people who wrote child-privacy law were picturing a child as the one being targeted by an ad, never as the one placing the bid that puts it in front of someone else.
Every major ad platform asks a new advertiser for a payment method, a billing address, and a campaign objective. None of them ask for proof of age, because the onboarding flow assumes whoever is opening an ads account is already an adult with a legitimate reason to be there: a small-business owner, a freelancer, a marketer buying inventory for a client. That assumption has gone unchallenged through most of digital advertising’s history because the economics rarely justified building a check against it. Age verification adds friction and cost for what platforms have long treated as a rare edge case rather than a routine risk worth engineering around, which is part of why, even after a six-figure case drew coverage across four continents, none of Google, Meta, TikTok, or Amazon has announced plans to add one.
This case argues that the assumption is weaker than the industry has priced in. A child who can read a campaign-setup wizard, choose a video to promote, and click through a budget field doesn’t need to defeat any security control to become an advertiser; the self-serve flow was built to make exactly that sequence as fast as possible for anyone holding the account open. Age checks exist elsewhere in commerce, for opening a bank account, signing a contract, or buying age-restricted goods, but nothing equivalent exists on the advertiser side of any self-serve ad platform. Building one would cut directly against the low-friction design every platform in this category has optimized for since self-serve advertising began, which is the more durable reason none of them are likely to add it, even now, weeks after the Mighty Mike Plays case put a precise number on what that gap can cost.
Google Ads does offer daily budget caps, campaign-level spending limits, and account-level billing alerts, all documented in the platform’s own support pages. In theory, a parent or an employer could set a hard daily ceiling that would have stopped a runaway campaign well short of six figures. In practice, none of those tools are turned on by default, and none of them are designed around the idea that the person creating the campaign might be a child using an adult’s saved card without the adult’s knowledge. Gagadget’s September 2026 reporting made this explicit, noting the campaigns ran without any mandatory budget cap or child-specific spending guardrail ever kicking in. The controls exist; the assumption that someone would proactively configure them before handing a 9-year-old access to a Google account did not hold.
This is the same structural gap that shows up across other kid-and-credit-card stories: the tools for prevention exist, but they require an adult to anticipate a scenario before it happens, rather than the platform catching it automatically once the spending pattern becomes obviously anomalous, such as multiple new campaigns launched within hours of each other from an account with no advertising history.
Large unauthorized charges run up by children on a parent’s saved payment method are not new. Mobile game microtransactions, console store purchases, and in-app purchases have produced years of stories involving four- and five-figure bills, usually triggering platform-level refund policies once a parent disputes the charges. What makes the Mighty Mike Plays case different is scale and mechanism. This wasn’t a loot box or a cosmetic skin bought on impulse. It was a child operating a self-serve advertising platform, the same tool marketing teams use to run real ad buys, and doing it repeatedly and deliberately over three weeks, not in a single accidental tap.
It’s also the first widely covered example this year of that spending pattern hitting a corporate card rather than a family one, which is what turned a family finance problem into an employment problem. A parent disputing a few hundred dollars in app-store charges with their bank is a private matter. A $118,000 unexplained charge on a company card triggers a finance department, a manager, and in this case, a termination. It also echoes the broader account-security conversation around kids’ gaming platforms, including the surge in Roblox account compromise cases tied to saved payment details and weak account separation between parents and children.
From a company’s perspective, an unexplained six-figure charge on an employee’s corporate card is a red flag regardless of the underlying cause. Finance and compliance teams are trained to treat unusual card activity as a potential fraud, embezzlement, or policy-violation event first, and sort out the sympathetic backstory second. Even once a company accepts that the spending came from a employee’s child rather than the employee personally, the corporate card agreement the employee signed typically makes them liable for any charges on that card, authorized or not, because the card was issued to them and it was their responsibility to secure it.
That’s the mechanism that turns a parenting mistake into a firing. It isn’t that the company necessarily believes Dave intentionally misused the card. It’s that corporate card policies are built around strict personal accountability precisely because “someone else used it” is the most common excuse in actual card-fraud cases, and treating a sympathetic version of that excuse differently would undermine the policy for everyone.
Corporate card policies are generally written as strict-liability agreements on purpose: the cardholder is responsible for every charge on the card, full stop, regardless of intent or circumstance. That structure exists because carving out exceptions for sympathetic explanations would invite every bad-faith cardholder to offer one. A claim like “my kid did it” is, from a policy-drafting standpoint, functionally the same category as “my card was stolen” or “a coworker borrowed it,” even though most people’s instinct is to treat a 9-year-old’s curiosity as obviously different from fraud. Companies that started making case-by-case exceptions for sympathetic stories would effectively be negotiating their own card agreements after the fact, which is why the policy tends to get enforced uniformly even in a case that reads, to almost everyone following it, as an honest mistake rather than misconduct.
Nothing in the reporting so far indicates Dave has pursued, or plans to pursue, a legal challenge to either his termination or the repayment demand, and as of early October 2026 there’s no public record of a lawsuit, an attorney statement, or a formal dispute filed on his behalf. But the situation raises genuine legal questions that go beyond whether the company’s position is sympathetic.
Corporate card agreements typically make the named cardholder personally liable for all charges, authorized or not, which is the clause most likely to get cited if the company pursues the debt formally rather than simply demanding it back within 30 days. Employment status is a separate question from the debt itself. In jurisdictions with at-will employment, a company generally doesn’t need a specific legal cause to terminate someone, and “an unexplained six-figure charge sat on your card for three weeks” easily clears whatever bar applies. Whether the termination itself was handled properly, including notice and documentation, is a different inquiry than whether the repayment demand is enforceable, and the reporting to date hasn’t addressed either in detail.
There’s also an underexplored wrinkle specific to this case: the charges were run up by a 9-year-old, not Dave. In most jurisdictions, minors lack the legal capacity to enter binding contracts, which in theory could complicate any claim pointed directly at the child, though that’s unlikely to matter in practice since no one is suing a 9-year-old. The liability question starts and ends with Dave, because the card was his, the Google account was his, and the company’s agreement was with him, not his son.
Losing a job over this story creates a second financial problem sitting underneath the headline number: unemployment benefits. Eligibility generally turns on how a separation gets coded, not simply on whether someone was let go. Employees laid off for business reasons typically qualify without much friction; employees terminated over documented misconduct or a serious policy violation often don’t, depending on the specific rules where they’re employed. An unexplained six-figure charge sitting on a corporate card for three weeks is exactly the kind of event an employer is likely to document as cause, even if everyone involved accepts that Dave’s 9-year-old, not Dave, was the one clicking “launch campaign.”
That distinction matters far more than it would in an ordinary layoff, because it determines whether Dave has any income replacement at all while the 30-day repayment clock runs. If his separation gets classified as for-cause, he could be dealing with the repayment demand and a benefits denial or delay at the same time, with no severance and no unemployment check to help bridge the gap. That double bind, a six-figure debt due in 30 days paired with a sudden loss of income rather than just one problem or the other, is a more complete explanation for why selling the family home has reportedly moved from a last resort to an active conversation.
None of this amounts to a wrongful-termination claim, which is a separate legal question from benefits eligibility and one the reporting to date hasn’t indicated Dave is pursuing. It’s simply the practical reality underneath a story that reads, on the surface, like a quirky viral anecdote about a kid and a credit card. Underneath that framing is a household managing a six-figure debt and a sudden loss of income at the same time, with a deadline attached to only one of the two problems.
The immediate financial impact of a single $118,000 ad bill is negligible to Google, which reported YouTube advertising revenue in the tens of billions of dollars annually in recent disclosures. But stories like this one carry outsized reputational weight for ad platforms because they surface a design gap that isn’t limited to one family. Any household or business where a saved card sits inside a shared Google account, and there are millions of them, has the same latent exposure. Expect renewed scrutiny of self-serve ad tools’ spending controls, similar to the periodic waves of criticism mobile app stores absorbed over child in-app purchases before Apple and Google tightened default settings and added purchase-confirmation prompts for minors.
For corporate finance and expense-management vendors, the story is a useful case study in why real-time spend alerts matter more than after-the-fact statement reconciliation. A three-week gap between the first unauthorized charge and detection is exactly the window that real-time transaction monitoring tools are built to close, and this incident will likely get cited in that sales pitch for months. It’s also a reminder that YouTube’s own advertising reach, part of the platform’s broader dominance detailed in comparisons like YouTube Gaming’s market share against Twitch and Kick, is large enough that even a child’s campaigns can buy real, measurable impressions.
Google isn’t the only platform where a saved card and an open account are treated as sufficient permission to spend. Meta’s Ads Manager, TikTok’s self-serve ad tools, and Amazon’s advertising platform all follow the same basic design: attach a payment method once, and any campaign created afterward can draw against it without a fresh authorization step tied to the size of the charge. Spending limits and budget caps exist on all of these platforms, the same as on Google Ads, but they share the same default-off weakness that let the Mighty Mike Plays bill reach six figures: nobody is required to turn the safety features on before they’re needed.
That makes this less a Google-specific failure than an industry-wide one built into how self-serve digital advertising works everywhere. Every major ad platform was designed to remove friction for small businesses and solo creators trying to promote content cheaply and quickly. None of them were designed around the possibility that the person clicking “launch campaign” might be a child who doesn’t understand that the number on the screen represents real money leaving a real account. Until that changes industry-wide, saving a work card to any shared account carries the same latent exposure Dave describes, regardless of which platform sits behind it.
Security and family-tech guidance converges on a short list of practical steps that would have interrupted this specific chain of events. First, never leave a work card saved inside a personal or shared Google account; use a dedicated account for business expenses with its own login. Second, set hard daily or campaign-level spending caps on any Google Ads account tied to a card you don’t want drained, even a small one, since the caps apply regardless of who is clicking. Third, turn on real-time transaction alerts through your bank or card issuer rather than relying on a monthly statement review, since alerts would have flagged the very first anomalous charge instead of the 118,000th dollar of it. Fourth, treat a child’s access to any account with a saved payment method the same way you’d treat access to the card itself, because in Google’s ad ecosystem, that’s functionally what it is. The same logic applies to locking down a child’s Minecraft server and account setup more broadly, since the game’s massive youth audience, still measured against rivals like Roblox and Fortnite in active player counts, makes it a constant target for both security risks and the kind of unsupervised spending seen in this case.
The same four steps apply whether the saved card sits behind Google Ads, Meta’s Ads Manager, TikTok, or Amazon Advertising, since none of them enable spending protections by default. A quick audit of every platform where a family or work card is saved, not just the one in this week’s headlines, is the more durable takeaway from this story than any single fix aimed at YouTube specifically.
A few outcomes look likely in the weeks ahead based on how similar stories have played out. First, expect Google to face renewed public pressure, even if informal, to add friction or confirmation steps to self-serve ad campaign creation once spending crosses an unusual threshold for a given account’s history, mirroring the purchase-confirmation prompts already common in app stores. Second, expect corporate expense-policy vendors and card issuers to reference this case in marketing material about real-time monitoring, since a three-week detection gap is an unusually clean example of the problem they sell solutions for. Third, given the scale of online attention the story has drawn, some form of negotiated repayment settlement between Dave and his former employer looks more likely than a full $118,000 lump-sum payment within the stated 30-day window, though nothing has been confirmed publicly.
Fourth, expect at least a handful of copycat “my kid ran up my card” stories to surface in the coming weeks, some real and some exaggerated, as the format proves it drives traffic. Fifth, don’t expect an official comment from Google or YouTube; the platform has stayed silent on similar family-spending controversies in the past, treating them as customer-support matters rather than public communications issues.
What makes this story resonate beyond a single family’s bad month is how ordinary the setup was. There was no exploit, no vulnerability, no stolen credential. A father did something millions of people do every day, save a card to a shared account, and a platform that was built to make advertising accessible to small creators did exactly what it was designed to do: let anyone with account access spend against that card with almost no friction. The system worked as built. It just was never built with the assumption that “anyone with account access” might be a 9-year-old who thought a repeatedly approved charge just meant the button worked.
A platform genuinely designed with this scenario in mind would likely look less like a single hard spending cap and more like step-up verification tied to an account’s own history: a first-time advertiser could be held to a low default ceiling until a human confirms they want it raised, the way anomaly-detection systems elsewhere in finance flag a transaction that breaks sharply from a customer’s normal pattern. A sudden run of same-day campaign launches from an account with zero prior ad history is exactly the kind of signal that could trigger a temporary billing hold pending confirmation, rather than clearing every charge instantly the way Dave’s son’s campaigns apparently did. None of that requires knowing who is physically clicking the button. It only requires treating a sharp break from an account’s own baseline as worth a pause, which is the one safeguard missing from every platform discussed in this story.
Reports put the total at $118,000, with IBTimes UK citing a more precise figure of $118,479.83 (about £88,493.73), spent over roughly three weeks on YouTube ad campaigns promoting his Minecraft and Roblox videos.
According to Tom’s Hardware, the charges went to a company credit card that the father, identified as David “Dave” Sarkisyan, had saved to his own Google account, which his son also had access to.
Yes. Dave himself says he was fired after the company discovered the charges, and his former employer is demanding full repayment of the $118,000 within 30 days. By October 2026, that account was no longer resting on Dave’s word alone: Dexerto and Yahoo both independently reported the job loss as fact, and Dexerto and iXBT.games both independently reported the 30-day repayment demand in the same direct terms.
There’s no public record as of October 2026 of Dave filing a legal challenge to either the termination or the $118,000 demand. Corporate card agreements typically hold the named cardholder liable for all charges regardless of who made them, and at-will employment rules in many jurisdictions don’t require a company to show specific cause to terminate someone over an unexplained six-figure charge.
No. Reporting indicates he has explicitly refused to set up a GoFundMe campaign or launch a cryptocurrency token tied to the story, saying instead that he plans to work off the debt conventionally.
No official statement from Google or YouTube has appeared in any of the reporting reviewed for this story, including the additional coverage from Dexerto, Yahoo, and The Register that emerged in October 2026. Coverage is based entirely on the father’s account, which Moneycontrol notes “has not been independently verified.”
Nothing in the reporting indicates Dave, his employer, or anyone else has requested a refund from Google, and ad platforms generally treat served impressions as billable once an auction clears, since that money has already been paid out to the publishers and creators whose inventory ran the ads. That makes a full refund unlikely even if one were requested, though it remains a question only Google could answer and has not addressed publicly.
Because the payment method was already saved to a Google account with no spending cap or alert configured, each new ad campaign could be created and funded with a few clicks, the same low-friction flow Google Ads offers any small creator or business.
Yes. Google Ads supports daily budgets, campaign-level spending limits, and billing alerts, but none of these are enabled automatically. They have to be configured in advance by whoever controls the account.
No. Meta’s Ads Manager, TikTok’s ad platform, and Amazon Advertising share the same basic design, a saved card plus an open account is treated as enough authorization to spend, with protective spending caps available but switched off by default.
Avoid saving work cards to shared or personal Google accounts, set hard spending caps on any advertising account linked to a card, enable real-time bank transaction alerts, and treat a child’s account access as equivalent to physical access to the card itself.
Elias Virtanen is the Cybersecurity Analyst at Tech Insider, bringing hands-on expertise from his background in penetration testing and security consulting. He previously worked as a security researcher at F-Secure in Helsinki, where he focused on threat intelligence and vulnerability disclosure. Elias covers ransomware trends, zero-trust architecture, and the evolving regulatory landscape including NIS2 and the EU Cyber Resilience Act. He holds a CISSP certification and an MSc in Information Security from Aalto University.
The Tech Insider Newsletter
Industry insights, the latest tech news, and special interviews, every week.

One email a week. No spam, unsubscribe anytime.
Tech Insider delivers in-depth coverage of the technologies shaping the future: AI, cybersecurity, cloud computing, hardware, and the trends that matter.
Tech Insider delivers in-depth coverage of the technologies shaping our future. From AI and cybersecurity to cloud computing and hardware innovation, our editorial team covers the trends that matter.
Tech Insider delivers in-depth coverage of the technologies shaping our future. From AI and cybersecurity to cloud computing and hardware innovation, our editorial team covers the trends that matter.
English | Svenska | Français | Suomi
We use cookies to measure traffic and improve Tech Insider. Read our Privacy Policy.
The Tech Insider Newsletter: industry insights, tech news, and special interviews.

source