[fritz]

Because those 61MB and the amount of obfuscation I ran an hybrid-analysis to have more details : https://www.hybrid-analysis.com/sample/e...592b428e2d
I personally wouldn't use that..

The following part Is somewhat concerning:

Possibly tries to implement anti-virtualization techniques

An In depth analysis Is required on the file.

If I was in charge I would just remove the link and provide few lines of code in any language that does the same thing 

I already spent too much time on this, nobody needs this level of protection and obfuscation for such a ridiculous program, it's literally 10 lines of code come one (I'm talking to whoever the dev is ^^) !
Some elements are definitively suspicious in hybrid-analysis report, although some might also be related to the crash report.. But I'm gonna save my time to analyse actually interesting programs 

[mothered]

Some elements are definitively suspicious in hybrid-analysis report, although some might also be related to the crash report..

Not targeted at yourself, but It's this^ that needs to be Identified and segregated, prior to making a decision on the link's removal.

[fritz]

Some elements are definitively suspicious in hybrid-analysis report, although some might also be related to the crash report..

Not targeted at yourself, but It's this^  that needs to be Identified and segregated, prior to making a decision on the link's removal.

I'm pretty confident mobsync.exe isn't involved in Microsoft crash report, if so then it's definitively malicious (see the part "Installs hooks/patches the running process").
But I can't be sure 100%... No that easy to find full (and readable) details on Windows processes sometimes.

[mothered]

I'm pretty confident mobsync.exe isn't involved in Microsoft crash report, if so then it's definitively malicious (see the part "Installs hooks/patches the running process").

I see your point and I've checked the report In detail.

I can't risk the probability of Infection, so I've removed the link.