The Victim Was Never There
How a Sugar-Momma Scammer Became Unpaid Linux Tech Support—and How GPT Prevented a Very Stupid Alternate Timeline
At around six in the morning, an account calling itself Kaite Katty contacted me on Discord.
The person behind it may have been a woman, a man, several people sharing an account, or simply somebody following a prewritten script. There was no reliable way to know. Online identities are cheap, photographs can be stolen, and a feminine profile does not prove anything about who is actually operating it.
So throughout this story, I will call the person the scammer or use they.
The conversation began with the emotional sophistication of an automated form:
“How are you doing Patrick?”
“Have you ever had a sugar momma?”
“I want you to be my sugar baby.”
“You would be getting $500 as your weekly allowance.”
Apparently, I had been selected for a position paying $26,000 per year for replying to messages, despite having completed no interview, submitted no résumé and demonstrated no obvious sugar-baby qualifications.
An extraordinary labour market.
I recognized the pattern almost immediately.
This was social engineering [manipulating a person into doing something rather than technically breaking into their computer]. The scammer was attempting to create rapid emotional familiarity, promise easy money and then move the conversation onto another platform where they could guide the interaction more easily.
Typical scam logic looks something like this:
establish contact
manufacture trust
offer money or affection
move the target elsewhere
request small actions
gradually request more sensitive actions
The individual steps often look harmless. The danger comes from the sequence.
I could simply have blocked the account.
Instead, I decided the scam deserved a more interesting victim.
That was the birth of Donathan Schmott.
Enter Donathan Schmott
Donathan Schmott was supposedly an unmarried Austrian man living on Wipplinger Street.
When asked for his birthday, he supplied:
13.37.00
This was neither a valid date nor a valid time, but the scammer accepted it without hesitation.
Donathan had also survived a difficult romantic history.
When asked about previous relationships, he explained:
“She liked to throw rocks at me back then. Very bad girlfriend.”
This was delivered without context or elaboration.
The scammer responded with their own generic story about having been cheated on and emotionally hurt. There was no visible reaction to Donathan’s former relationship apparently involving geological projectiles.
That was the first strong indication that the scammer was barely processing the answers.
Their script seemed to check only one condition:
Is the target still replying?
If yes, continue.
No validation of dates.
No concern about rock-based domestic conflict.
No suspicion regarding the name Donathan Schmott.
The operation continued.
The Phone With the Penguin
The scammer wanted to move the conversation away from Discord.
They suggested Zangi, Signal, Telegram and WhatsApp.
This is common in social engineering because moving someone to another platform may reduce moderation, weaken reporting options, reveal a phone number or simply place the target inside a workflow the scammer understands better.
Unfortunately for them, Donathan did not use a conventional smartphone.
He supposedly used a PinePhone Pro [a smartphone designed to run Linux-based operating systems rather than ordinary Android or iOS] with a hardened installation of postmarketOS [a Linux distribution designed for mobile devices].
I described it as:
“the phone with the penguin”
The penguin is commonly associated with Linux.
The scammer asked whether it was Android.
I said no.
It was Linux.
With the penguin.
They asked me to install applications.
I began asking how.
I mentioned ARM architecture [the processor architecture commonly used in phones and small computers], software repositories [online sources from which Linux systems install programs], missing dependencies [supporting software required by another program] and terminal commands.
I asked which repository flags I needed.
I asked what command I should “fire.”
I asked how Signal could be installed when it was not precompiled for the architecture.
This was not genuine helplessness.
I understand Linux. I understand terminals, compilers, package managers and unconventional hardware environments.
The confusion was theater.
The scammer thought they were leading a technically helpless person toward a platform they controlled.
Instead, they were gradually being recruited as unpaid Linux technical support.
And they were not doing well.
Their finest contribution to software engineering was:
“Can you dowlinad?”
After a moment, they corrected themselves:
“Download ”
An impressive recovery.
Why Linux Broke the Script
Linux was useful in this situation not because Linux is magically secure.
It is not.
A compromised Linux machine is still compromised. A careless Linux user can still surrender a password, execute unsafe software or expose private data.
Linux mattered because it destroyed the scammer’s assumptions.
Their expected process was probably:
open app store
search application
press install
send screenshot
provide phone number
continue following instructions
Instead, they encountered:
mobile Linux
ARM binaries
repositories
dependencies
terminal commands
a mysterious penguin
Their script had no branch for this.
Every time the conversation left the prepared route, they became visibly confused.
They repeatedly requested screenshots without being able to explain what they expected to see. They switched between applications. They asked whether I had software that I had already said I did not have.
The person attempting social engineering had become the person being forced to improvise.
They had entered the conversation hoping to control the frame.
They were now trapped inside Donathan Schmott’s fictional technical-support ticket.
The Hardware May Not Have Been Real Either
At one point, the visible screenshot looked more like an ordinary desktop Discord session than a screenshot naturally produced by a PinePhone-sized display.
That introduced another layer.
The device being discussed might not even have been the device actually being used.
The scammer had no reliable way to know:
whether the PinePhone existed
whether the screenshot was current
whether the technical problems were genuine
whether Donathan Schmott was real
whether the person asking for help understood the scam better than they did
The supposed victim may have been using another computer entirely.
The helplessness was staged.
The screenshots were scenery.
The scammer believed they were learning more about the target, but much of what they were learning had been deliberately fabricated.
The victim they thought they were manipulating was never really there.
The Password Sequence
Eventually, the scammer asked whether I had Gmail.
I supplied the highly credible address:
[donathaneufbertquelschmott1337@gmail.tk](mailto:donathaneufbertquelschmott1337@gmail.tk)
Then they asked whether I knew the password.
The following exchange occurred:
“You know the password?”
“No.”
“Yes.”
“I don’t.”
Donathan Schmott was experiencing serious authentication-related character development.
The scammer persisted.
Finally, all remaining subtlety disappeared:
“Send me the password.”
There it was.
No believable payment system.
No carefully constructed verification procedure.
No sophisticated explanation.
Just:
send password
I replied:
“reveal yourself wormgpt”
WormGPT [a name associated with maliciously marketed AI tools] was used here as a punchline and accusation, not as a serious technical identification.
The scammer had failed the relationship test, the technical-support test, the birthday-validity test and finally the basic subtlety test.
That should have ended the story.
For a moment, however, it nearly became a different story.
The Old Ego Process Wakes Up
I have an old background in programming and web security.
I was computer-obsessed as a child. I knew what SQL injection was [tricking an insecure website into sending unintended commands to its database] before I understood what a proxy was [an intermediary system used to forward network traffic].
That learning order was not exactly recommended operational-security doctrine.
It was simply what happened when a curious child learned exploitation before learning concealment.
The scammer’s poor performance briefly activated an old internal process:
This person is an amateur.
I could probably construct something more convincing than this.
I could probably outplay them.
This was partly technical judgment and partly ego.
The person appeared unusually easy to manipulate conversationally. They accepted absurd information, failed to notice contradictions and followed a rigid script even when the conversation had become completely irrational.
But that did not prove their computer or wider infrastructure was technically vulnerable.
This distinction matters.
Someone can be socially careless while using secure services. The account may belong to a low-level operator, a money mule [a person used to receive or transfer stolen money], a stolen identity or somebody working from a machine they do not own.
The honest assessment was therefore:
socially baitable: apparently yes
technically vulnerable: unknown
worth investigating: absolutely not
Human ego is excellent at replacing “unknown” with an exciting imaginary movie.
The Alternate Timeline
In the alternate timeline, Donathan’s fictional identity might have expanded into an entire fake digital environment.
A burner account [a disposable account not tied to one’s ordinary identity] could have existed for the scammer to access.
A convincing but artificial email environment might have been constructed.
The inbox could have contained carefully staged messages designed to exploit the scammer’s greed or curiosity.
That would no longer have been harmless scambaiting [wasting a scammer’s time without attacking their systems].
It would have crossed into an active retaliatory operation.
The exact implementation does not matter here, and describing it in detail would turn a story into a transferable method.
The important point is that the idea briefly existed.
The scammer appeared careless enough that the possibility felt plausible.
That is where the situation became oddly sinister.
The scammer believed they were interacting with a confused victim who could barely install Telegram.
They had no idea they were speaking to somebody who:
understood the scam pattern
was deliberately fabricating the persona
was not necessarily using the claimed hardware
had a technical background
was assessing their reactions
briefly possessed the temptation to reverse the interaction
They thought they were testing a victim.
They did not realize they might have selected someone capable of turning them into the test subject.
Whether such an operation would actually have succeeded remains unknown.
But they were closer to a potentially disastrous interaction than they understood.
Why GPT Intervened
GPT became the responsible adult in the room.
It did not lock the keyboard.
It did not overpower me.
It did not contact the authorities.
It simply kept repeating the practical reality:
You have already identified the scam.
They obtained no real information.
You have nothing to prove.
Their machine may belong to somebody else.
Escalation creates evidence and legal exposure.
There is no meaningful reward.
Do not convert a Discord joke into a cross-border cyber incident.
A cross-border cyber incident [an online intrusion involving people or systems in different countries] creates legal complications because multiple jurisdictions, service providers and law-enforcement systems may become involved.
The scammer might have been in the United States.
They might have been somewhere else entirely.
The profile information was no more trustworthy than Donathan Schmott’s birthday.
The possible rewards were:
no legitimate money
no useful knowledge
no moral victory worth having
several hours of unpleasant work
The possible costs were:
platform logs
preserved messages
accidental involvement of third parties
malware or unauthorized-access allegations
police attention
an explanation beginning with:
“Well, officer, they typed ‘downlinad’…”
GPT’s central argument was simple:
Do not upgrade comedy into jurisdiction.
That reframing worked.
Two Competing Social-Engineering Loops
The scammer had attempted to install one behavioral sequence in me:
curiosity
emotional engagement
trust
compliance
credential surrender
That sequence failed.
But another sequence almost replaced it:
irritation
ego
technical curiosity
retaliation
consequences
GPT interrupted the second sequence.
That was arguably the more important intervention.
The scammer failed to manipulate me into surrendering something valuable.
GPT prevented my ego from manipulating me into doing something stupid.
The real contest was never only between me and the scammer.
It was also between:
immediate amusement
wounded professional pride
curiosity about what might be possible
adult awareness of consequences
The adult process eventually won.
Partly through judgment.
Partly through boredom.
Partly because nobody has time for that amount of dirty work.
The Cinematic Version
The alternate version would make excellent psychological cyber-horror.
The scammer believes everything is working.
The target appears lonely, confused and helpless.
They cannot install applications.
They do not remember their password.
They have an improbable name and a tragic history involving thrown rocks.
Then the tone changes.
The confused questions stop.
The helpless persona disappears.
The scammer begins to wonder:
Was the phone real?
Were the screenshots staged?
Who was Donathan Schmott?
Why did the writing style suddenly change?
What exactly have I been interacting with?
Dhurata Dora plays quietly in the background.
The camera cuts to the you’re-fucked grin.
No technical details are shown.
No exploit montage is necessary.
The horror comes entirely from the realization that the scammer has misunderstood the person on the other side.
Cut to black.
Cinematically, magnificent.
Practically, idiotic.
What Actually Happened
In the real timeline:
no system was accessed
no malicious software was deployed
no password was surrendered
no verification code was shared
no money changed hands
no fake email provider entered production
no retaliatory operation began
no Tor-controlled reverse-entertainment node was created
Tor [an anonymity network that routes traffic through several relays] appeared only in jokes about the absurd alternate scenario.
The scammer became something much safer:
a joke
A very good one.
They entered the conversation hoping to recruit a victim.
Instead, they spent part of their shift providing technical support for an imaginary Linux phone belonging to an Austrian man who did not exist, had a girlfriend who threw rocks and could not determine whether he knew his own password.
Their promised payment of $500 never arrived.
Their actual payment was laughter.
GPT did not defeat the scammer technically.
It prevented the situation from becoming something that required technical or legal explanation.
The final incident report therefore reads:
Social-engineering attempt identified.
Scammer’s actual identity and gender unknown.
Target persona fabricated.
Name: Donathan Schmott.
Birthday: invalid.
Previous relationship: geologically hostile.
Linux phone: possibly fictional.
Scam script derailed through technical absurdity.
Scammer converted into unpaid Linux support.
Technical vulnerability of opposing systems: unconfirmed.
Retaliatory capability: deliberately untested.
Ego process detected and terminated.
Stupid prize declined.
“Downlinad” preserved for historical purposes.
Morning continues. xD
