x001xs

Dark since March 13, 2022
1 victim named on the leak site
0 in the last 30 days
0 in the last 12 months
Mar 2022 first victim we recorded
Mar 13, 2022 most recent victim posted
1 leak site tracked

Data as of August 16, 2026.

The one x001xs victim

VictimSectorCountryPosted
bmibaku.azNot identifiedNot identifiedMar 13, 2022

Browse recent data breaches for more.

x001xs leak site

The address we've seen x001xs publish victims from. Any .onion address needs the Tor Browser.

  • nalr2uqsave7y2r235am5jsfiklfjh5h4jc5nztu3rzvmhklwt5j6kid.onion

x001xs questions

Is x001xs still active?

Not for over a year. The last victim we recorded was March 13, 2022. The leak site has published nothing since, though the data it already leaked is still out there.

How many victims has x001xs claimed?

x001xs has named 1 victim on its leak site since we started tracking it. That counts organizations, not leaked files. A single victim often accounts for thousands of published files.

When did x001xs first appear?

The first victim we recorded for x001xs was posted on March 13, 2022. That's when the group entered our collection, which isn't necessarily when it started operating.

Has x001xs already got your credentials?

Check whether your employees' logins have leaked on the dark web before they're exploited.

Check your exposure →

Continuous dark web monitoring alerts you when your company's data shows up, whether that's employee credentials or files published after an attack.