nostr:npub1sdtvw8y3yhksws5jf8ttl45vru06krpuuus2fys3u5exucvc4ywquf96z3 nostr:npub1074dk2mqqxl7kgukea6th3xaa9fdgx7vty2x8zger32uydyf6e3qzhz2j6 As I read it, they didn't trigger the dump; they discovered it while on the machine with access to the debugging environment. This [compromised] account had access to the debugging environment containing the crash dump which incorrectly contained the key.