The address in question is a multi-signature address and has been generated using three different public keys.
I don't know how, but it should be possible to derive all the three public keys from data of a transaction made from that address.
OP you may want to ignore this post as it may be a little off topic but it got me thinking,Supposedly its possible, however I haven't found a great solution. If I do, I'll let you know.
Ive messed with all the mergers/calculators like
https://github.com/ThePiachu tools
One of the problems with vanity addresses is that there are 6 derivatives from 1 key.
Finding the others first is a common problem.
I used to wonder though,
if each derivative is in fact a new master key to a new set of 6 derivatives
and some type of formula is found to solve for all 6 derived keys from a master key wouldn't this potentially compromise some security?
for example, find an accurate child derivative sum it up somehow for the master sum then the master sum gives access to all the child derivatives?
I've often wondered if this were made possible and each derivative is also a master key with a set of derivatives if crawling this structure would have overlapped another
set of keys in use. (a collision approach?)
If Infinity= 0
Infinity x Infinity= 0
Infinity/6^6= 0Even if, everything's still all good however collision possibilities still increase. (I think?

)
I found this a while back while researching BTC pay servers.
ExtKey masterKey = new ExtKey();
Console.WriteLine("Master key : " + masterKey.ToString(Network.Main));
for (int i = 0 ; i < 5 ; i++)
{
ExtKey key = masterKey.Derive((uint)i);
Console.WriteLine("Key " + i + " : " + key.ToString(Network.Main));
}
Master key :
xprv9s21ZrQH143K3JneCAiVkz46BsJ4jUdH8C16DccAgMVfy2yY5L8A4XqTvZqCiKXhNWFZXdLH6VbsCs
qBFsSXahfnLajiB6ir46RxgdkNsFk
Key 0 :
xprv9tvBA4Kt8UTuEW9Fiuy1PXPWWGch1cyzd1HSAz6oQ1gcirnBrDxLt8qsis6vpNwmSVtLZXWgHbqff9
rVeAErb2swwzky82462r6bWZAW6Ty
Key 1 :
xprv9tvBA4Kt8UTuHyzrhkRWh9xTavFtYoWhZTopNHGJSe3KomssRrQ9MTAhVWKFp4d7D8CgmT7TRza
uoAZXp3xwHQfxr7FpXfJKpPDUtiLdmcF
Key 2 :
xprv9tvBA4Kt8UTuLoEZPpW9fBEzC3gfTdj6QzMp8DzMbAeXgDHhSMmdnxSFHCQXycFu8FcqTJRm2ka
mjeE8CCKzbiXyoKWZ9ihiF7J5JicgaLU
Key 3 :
xprv9tvBA4Kt8UTuPwJQyxuZoFj9hcEMCoz7DAWLkz9tRMwnBDiZghWePdD7etfi9RpWEWQjKCM8wH
vKQwQ4uiGk8XhdKybzB8n2RVuruQ97Vna
Key 4 :
xprv9tvBA4Kt8UTuQoh1dQeJTXsmmTFwCqi4RXWdjBp114rJjNtPBHjxAckQp3yeEFw7Gf4gpnbwQTgDp
GtQgcN59E71D2V97RRDtxeJ4rVkw4E
Key 5 :
xprv9tvBA4Kt8UTuTdiEhN8iVDr5rfAPSVsCKpDia4GtEsb87eHr8yRVveRhkeLEMvo3XWL3GjzZvncfWVK
nKLWUMNqSgdxoNm7zDzzD63dxGsm
https://finbuzzactu.files.wordpress.com/2017/06/blockchain-programming-in-csharp.pdf