Malware embedded into audio driver is silently recording from system mic
twitter.com

・

61 points

・

CGMthrowaway

・

20 hours ago

17 comments

jml7c5 ・ 19 hours ago

According to the vx-underground Twitter account, this is just Regin (which was first described in 2014): https://x.com/vxunderground/status/1995309917805179141

https://en.wikipedia.org/wiki/Regin_(malware)

  • bri3d ・ 19 hours ago

    I’m not even convinced the audiod thing is Regin; whatever is going on is way less sophisticated even based on what the OP posted from volatility. I don’t think the hash they gave vx-underground is even from the sample from the original screenshots.

    I think this person is just karma/clout farming badly and the screenshots are of some even more basic RAT.

  • ashleyn ・ 18 hours ago

    Well at the very least he confirmed Regin continues to circulate.

    • unsnap_biceps ・ 18 hours ago

      He hasn't actually confirmed that the image he's processing is recent or if it was a test image and by "I found", he means he was able to find the thing that was known to be there. The Twitter thread has some people asking for clarification and none have been received yet.

bri3d ・ 19 hours ago

I’m not sure this isn’t just some garden variety RAT that was named “audiod.exe”? The author seems kind of confused; there’s nothing driver related I can see here. They claim the malware was “injected” into a legitimate process, but the Microsoft audio graph process is “audiodg.exe”

jacquesm ・ 19 hours ago

That's an OVH Singapore IP, did they flag this to OVH? That server should be taken offline and the contents preserved for forensics.

  • monerozcash ・ 18 hours ago

    They're analysing a file from 2012, OVH probably didn't even own those IPs back then.

    • jacquesm ・ 14 hours ago

      So this whole post is BS then.

efilife ・ 19 hours ago

I quickly skimmed at through twitter and youtube profiles and it's apparent that this guy has no idea of what he's talking about

  • irilesscent ・ 16 hours ago

    What makes me suspect them the most was the fact that they use pure neon green text on black as their tty color. (seriously who does that?)

  • ugh123 ・ 17 hours ago

    I actually get that impression too. There's a surprising lack of detail for what he's trying to announce as a major exploit and feat of discovery.

  • efilife ・ 4 hours ago

    lol the amount of typos here is abysmal, I must have been half-asleep

fishgoesblub ・ 19 hours ago

"compressed .wav files"

Interesting that the malware author isn't using actual compressed audio (No idea why the Twitter poster seems to think wave files are compressed) I would assume that you'd want to transmit as little data to evade detection.

  • RossBencina ・ 16 hours ago

    .wav files are RIFF containers of type 'WAVE'. These files can contain many different types of RIFF chunks, but the required chunks are a 'fmt ' (format information) and 'data' (audio payload). The format chunk describes the encoding of the audio payload data, among other information (channel count, sample rate).[0]

    Although .wav files are, today, typically used for non-compressed PCM data (WAVE_FORMAT_PCM), even the original 1991 RIFF specification allowed for three compressed formats: mu-law, a-law, ADPCM.[1] These are all efficient to compute and I don't find it completely implausible that such low quality compression would be used. Modern .wav files may use the WAVEFORMATEX or WAVEFORMATEXTENSIBLE chunk, which uses GUIDs to identify formats. It supports the original compressed WAVE formats,[2] but also more modern compressed formats. Here is For example, here is Microsoft's list of sub-format GUIDs (includes MPEG formats and AC-3):

    https://learn.microsoft.com/en-us/windows-hardware/drivers/a...

    [0] https://en.wikipedia.org/wiki/WAV

    [1] https://www.aelius.com/njh/wavemetatools/doc/riffmci.pdf heading "WAVE Format Categories".

    [2] https://learn.microsoft.com/en-us/windows-hardware/drivers/d...

  • irilesscent ・ 16 hours ago

    I think its more resource intensive to record a more optimised format.

snorbleck ・ 17 hours ago

you'd think the whole "micmon.dll" reference would give it away...