#Acestream soda player code#

Could it be? Sure! I am not saying it was 'clean', but there isn't any real evidence the program was doing much of anything other then verifying cache data. There is NOTHING About what OP Posted that is malicious or 'weird' unless you don't have any real understanding of how programs interact with memory and files. Yes, it even could be malicious, but then why isn't EVERYONE having this issue? Why only 2 people? It could have been anything, honestly, it could have just been a process gone fucking awry.

#Acestream soda player code#

It might be scanning for an alternate config file that one of the devs was using on the fly and forgot to remove the code for, it could have been a test for streaming protected content paid for through their app that went haywire. Scanning files doesn't mean its reading them, it doesn't mean its opening them, it just means that its scanning memory footprints. ONE person has UNVERIFIABLE screenshot that Soda was accessing files, and even then, its not really 'Doing' anything malicious.I don't know what to say really, just reading all this. But it seems that they are not intending to answer so far.

None the less, i would really like for the team behind sodaplayer to take this incident seriously, i know others have pinged them, and i have also tried to send them a link to this post also, via their website. It can be remotely disabled, or perhaps, it can be remotely triggered Ontop of this, i tried to reproduce today without luck, while streaming another acestream link for quiet a while, so either maybe one of the following is true: I cannot find a reason why it should have a feature doing this kind of file access at all.

In this context i opened up the details which displayed open file descriptors to these private word documents, ontop of the presumed access to my keybase files.

This lead me to investigate the processes in the activity monitor - where Soda stream had a subprocess, the one showed in OP, with a large number of bytes read from disk. It was discovered as i, after a while of streaming, got a keybase client warning, that a program had accessed the private shared folder shared between me and a number of my connections on the platform. The incident was discovered while my setup was streaming while streaming F1 via acestream.