MyRecon OSINTALIEN TXTBASE Stealer Logs
Behind the exposed accounts
In February 2025, 23 billion rows of stealer logs were obtained from a Telegram channel known as ALIEN TXTBASE .
Follow the story
On 15 February 2025, ALIEN TXTBASE Stealer Logs was breached. 284,132,969 accounts were exposed, including email addresses, passwords. MyRecon rates it 84/100, critical. That is roughly everyone in Brazil.
How the story unfolded
Open a step to read the detail. Missing dates stay unknown.
02Entry point
The records came from information-stealing malware on people's devices, rather than a single company database.
03Discovery and disclosure
A separate discovery or company-disclosure date is not established by this feed record.
04Added to the breach catalogue
2025-02-25. This is the catalogue date, not necessarily the disclosure date.
05Reported outcome
284,132,969 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Passwords.
This is not a company's breach and reading it as one gets the response wrong. Stealer logs come from malware running on individual people's own computers, recording credentials as they are typed. If your address appears here, no service failed you. A machine you used was infected, and everything entered on it during that period should be assumed captured.
What makes a stealer log more dangerous than an ordinary credential dump is the third column. A leaked password list tells an attacker a password you once used. A stealer log tells them the password, the website it was entered into, and the email address that goes with it, a working login rather than a guess. Credential stuffing becomes unnecessary when the file already says where the key fits.
So the action here is different from every other entry in this archive. Changing one password is not the fix. Clean the device first, because otherwise the new password is captured too, then rotate credentials starting with email and anything financial.
The story behind the breach
In February 2025, 23 billion rows of stealer logs were obtained from a Telegram channel known as ALIEN TXTBASE . The data contained 284M unique email addresses alongside the websites they were entered into and the passwords used. This data is now searchable in HIBP by both email domain and the domain of the target website.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
How did it happen?
The records came from information-stealing malware on people's devices, rather than a single company database.
What was the motive?
The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
What was the outcome?
284,132,969 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Email addresses, Passwords.
What was exposed, and why it matters
Email addresses
The address becomes a confirmed, active target, expect more phishing, better aimed.
Passwords
Anyone reusing this password elsewhere has those accounts exposed too, credential stuffing is automated and tries them all within days.
What to do if you were in it
Questions people ask about this breach
Was my email address in the ALIEN TXTBASE Stealer Logs breach?
Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.
What data was leaked in the ALIEN TXTBASE Stealer Logs breach?
email addresses, passwords. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 15 February 2025. It was published to Have I Been Pwned on 25 February 2025, a gap of 11 days during which the data was already out.
Is the ALIEN TXTBASE Stealer Logs breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
284,132,969 accounts. That is roughly everyone in Brazil. That is accounts rather than people, one person often has several.
Read next
Also in the archive
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.