Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Testing
Malware Hub: Statistics and Reports
Windows Defender - June 2019 Report
Message
<blockquote data-quote="Andy Ful" data-source="post: 828758" data-attributes="member: 32260"><p>[USER=51905]Evjl's Rain[/USER] ,</p><p>The screenshots from your test <a href="https://malwaretips.com/threads/malware-samples-17-9-08-2019.94252/post-828668" target="_blank">https://malwaretips.com/threads/malware-samples-17-9-08-2019.94252/post-828668</a> suggest, that after reboot the system is not infected. There is one leftover in the registry (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) which tries to run the payload (JAR file) on Windows start. That is why javav.exe is present in Process Explorer. This action fails because the payload was detected and already removed by WD.</p><p>The system is <span style="color: rgb(184, 49, 47)"><strong>not clean</strong></span>, but there is no evidence of an active & malicious code running.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up (y)" loading="lazy" data-shortname="(y)" /></p><p>[ATTACH=full]219438[/ATTACH]</p><p></p><p>I noticed the same behavior in some other tests about WD, where the final status was infected, but in fact, it was not clean (with similar leftovers in the Registry).</p><p></p><p>Edit.</p><p>Such a leftover in the registry is not dangerous at all and does not contain any malicious code. </p><p>If one has a file leftover (not active) on disk, then this would be more dangerous, because the user could accidentally run the malicious file - but as I can see in such cases, the system is qualified on MH as not infected (not clean).<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure :unsure:" loading="lazy" data-shortname=":unsure:" /></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 828758, member: 32260"] [USER=51905]Evjl's Rain[/USER] , The screenshots from your test [URL]https://malwaretips.com/threads/malware-samples-17-9-08-2019.94252/post-828668[/URL] suggest, that after reboot the system is not infected. There is one leftover in the registry (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) which tries to run the payload (JAR file) on Windows start. That is why javav.exe is present in Process Explorer. This action fails because the payload was detected and already removed by WD. The system is [COLOR=rgb(184, 49, 47)][B]not clean[/B][/COLOR], but there is no evidence of an active & malicious code running.(y) [ATTACH type="full" alt="Windows 10 x64-2019-08-10-03-15-45.png"]219438[/ATTACH] I noticed the same behavior in some other tests about WD, where the final status was infected, but in fact, it was not clean (with similar leftovers in the Registry). Edit. Such a leftover in the registry is not dangerous at all and does not contain any malicious code. If one has a file leftover (not active) on disk, then this would be more dangerous, because the user could accidentally run the malicious file - but as I can see in such cases, the system is qualified on MH as not infected (not clean).:emoji_thinking: [/QUOTE]
Insert quotes…
Verification
Post reply
Top