Event JSON
{
"id": "93f3a6b0c8acb34830b871dddb8a0c0224b90dd0aef92b5a0ef5a24d75e9e7bf",
"pubkey": "b1c21eeaaeae0176c2c0c48524ce9135d7cce43129535931e03a14eee45e339a",
"created_at": 1713892920,
"kind": 1,
"tags": [
[
"p",
"f7d0478e54eaa6e0cc98adf81d712148bce169a2c21b1c0f7a4ed446c6adc09e",
"wss://relay.mostr.pub"
],
[
"p",
"f6870afcde4480ec8508f50304859e14a51309ff24ab3f0f862c52bdc4af8747",
"wss://relay.mostr.pub"
],
[
"e",
"d5de281e2b640f32baff4dce70a1e59b605e00d8dbf1134885a0cb3e4fc6c341",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/ciphermonger/statuses/112321686465913456",
"activitypub"
]
],
"content": "nostr:npub17lgy0rj5a2nwpnyc4hup6ufpfz7wz6dzcgd3crm6fm2yd34dcz0qlk9uux Eh, I would argue that's not completely unique to Veeam and has more to do with how the backups are stored. I've seen attackers try and fail (hard) to nuke backups on a properly hardened repository.",
"sig": "f1c8f49ed1f92d4631cd7f59d83bd51da02f95977b96462342503aa38dd96bebfb8ec2f302316f0b7c76ab7158cdd58d820a146b3d94ca40cd9c052055f7a80d"
}
