the first string is a cryptographic hash or data. it could be md5, but not necessarily. 32 chars = 128bit is correct length for md5, but it could be anything really. 128bit is also block length for AES cipher, so these could be chunks of encrypted data.
more interesting is the ID: Number. someone purposefully created a message with an id: number in it. so what was the purpose and what is the number?
it appears in this picture that number is counting down 20 -19 … but sample is too small to confirm. would be interesting to check other samples.
if this is AES encrypted data number could be the counter used with AES-CTR encryption but you never reuse the same counter in an encrypted stream so if that was the case we are looking at multiple streams of encrypted data.
now other question is how did this get blasted to real people.
if this was not intentional, then most likely scenario is a developer with unrestricted access running a program that they believed was running in an offline environment but actually ran live.
there are a number of different possible scenarios:
they were testing blasting random messages to large numbers of people.
they were testing blasting messages to specific people but the target ids configured in the offline environment were different than the live environment so when they ran the program live the messages went to the wrong people.
just speculations