LV Blog

Dark since October 6, 2022
Also tracked as LVBlog
60 victims named on the leak site
0 in the last 30 days
0 in the last 12 months
Mar 2021 first victim we recorded
Oct 6, 2022 most recent victim posted
8 leak sites tracked

Data as of August 16, 2026.

Credential exposure before the attack

58.3% of LV Blog victims whose domain we can identify (35 of 60) had employee credentials leak in the 12 months before LV Blog named them as a victim.

We don't know whether any of these credentials were how LV Blog gained initial access.

What industries LV Blog targets

Sector identified for 3 of 60 victims.

Manufacturing1
Real Estate1
Logistics1

Where the victims are located

Country identified for 27 of 60 victims.

Australia6
France5
Japan4
Brazil3
Malaysia3
Mexico1
Canada1
Turkey1

Most recent LV Blog victims

VictimSectorCountryPosted
capecodrta.orgLogisticsNot identifiedOct 6, 2022
silterra.comManufacturingMalaysiaJun 6, 2022
xytechsystems.comNot identifiedNot identifiedMay 26, 2022
amethyst-radiotherapy.comNot identifiedNot identifiedMay 24, 2022
cpqd.com.brNot identifiedBrazilMay 2, 2022
motiveenergy.comNot identifiedNot identifiedMay 1, 2022
importadortrujillo.com.ecNot identifiedNot identifiedApr 17, 2022
omniplussystem.comNot identifiedNot identifiedFeb 18, 2022
gruporoveri.com.brNot identifiedBrazilFeb 16, 2022
tikg.co.jpNot identifiedJapanFeb 14, 2022
lhotellerie-restauration.frNot identifiedFranceJan 28, 2022
wagstaff.comNot identifiedNot identifiedDec 31, 2021
reliancenj.comNot identifiedNot identifiedDec 20, 2021
benlineagencies.comNot identifiedNot identifiedDec 17, 2021
agrofair.nlNot identifiedNetherlandsDec 16, 2021
tt-network.dkNot identifiedDenmarkDec 13, 2021
kobebussan.co.jpNot identifiedJapanDec 12, 2021
jpbdselangor.gov.myNot identifiedMalaysiaDec 11, 2021
tlpterminal.com.myNot identifiedMalaysiaDec 9, 2021
gaben.czNot identifiedCzech RepublicDec 6, 2021

Showing the 20 most recent of 60. Browse recent data breaches for more.

LV Blog leak sites

Addresses we've seen LV Blog publish victims from. Any .onion address needs the Tor Browser.

  • rbvuetuneohce3ouxjlbxtimyyxokb4btncxjbo44fbgxqy7tskinwad.onion
  • lno6zx3doe3nki3txgoo7ocsm37vdg46lshqmgqhn5swqgsxuz2fo4id.onion
  • nddzpcc6yh3z3zkdvd7y5ycjasgiwd33hpqlutl65vwe3zjdai2j6xyd.onion
  • 3gtlnuzgyeondzqptzndtpnp3fczacziga3njyzy52bm76kyuw2oxyad.onion
  • 4aenqyz7gnhjokk3rmjrjl7epudaqbxqzno5np57dfo6bbqlkq7uh5ad.onion
  • envecpivgmvjpiu7wspm7yrmgumoj5esu5q2rjp6a5dlq2mjwhoxq3id.onion
  • piwr2fyfximgezlu6todjhess4zn637crn7j64tlmsljs5tawhopniyd.onion
  • dquf4y4bdexjzdi42vbyyl56hp4u54p7gbvmw4kqvcvqzmq5vpaq7vid.onion

LV Blog questions

Is LV Blog still active?

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

How many victims has LV Blog claimed?

LV Blog has named 60 victims 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 LV Blog first appear?

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

Has LV Blog 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.