Endpoint Protection Small Business Edition

 View Only
Expand all | Collapse all

Attack: Ransom.Gen Activity 22

  • 1.  Attack: Ransom.Gen Activity 22

    Posted Jun 18, 2018 01:07 PM

    Hi there, I'm receiving this alert al least 40 times in a week (week-ends the most) It seems that is an internal issue as I'm behind a firewall and both, the attacker and the target are part of the network. I really appreciate comments and support. 

     

    Luis

     

    A high-risk intrusion was detected on PC within group Default Group on 6/18/2018 11:44:59 AM.
    IPS Alert Name
    Attack: Ransom.Gen Activity 20
    Status
    Blocked
    Attack Signature
    N/A
    Targeted Application
    N/A
    Targeted IP
    192.168.1.2
    Targeted Port Number
    445
    Targeted Host Name
    SERVER


  • 2.  RE: Attack: Ransom.Gen Activity 22

    Posted Jun 18, 2018 05:29 PM

    Have you taken the attacking computer offline and performed analysis to determine what is going on with it? That is an internal IP address, which seems to be infected and attempting to spread to other internal machines.



  • 3.  RE: Attack: Ransom.Gen Activity 22

    Posted Jun 18, 2018 09:21 PM

    Hi Brian, well I have done trillions of scans on those machines (because is not only one) but nothing is detected; nevertheless, they are online.. I've never done the scan offline. 

    Thanks



  • 4.  RE: Attack: Ransom.Gen Activity 22

    Posted Jun 18, 2018 09:26 PM

    Hi Brian, I've done trillions of full scans in those computer (cuz is not only one) and nothing is detected. Nevertheless, they were online when I scanned them; even Symantec triggers a full scan after the blocking event. Does it make diference having done the scan online?

    Many thanks

    Luis 



  • 5.  RE: Attack: Ransom.Gen Activity 22

    Posted Jun 18, 2018 09:27 PM

    Hi Brian, I've done trillions of full scans in those computer (cuz is not only one) and nothing is detected. Nevertheless, they were online when I scanned them; even Symantec triggers a full scan after the blocking event. Does it make diference having done the scan online?

    Many thanks

    Luis 



  • 6.  RE: Attack: Ransom.Gen Activity 22

    Posted Jun 20, 2018 07:46 AM

    Try disabling SMBv1 and SMBv2 on machine.



  • 7.  RE: Attack: Ransom.Gen Activity 22

    Posted Jun 26, 2018 07:47 PM

    Hi am getting this to, run a million scans nothing 

    same scenario as Luis 



  • 8.  RE: Attack: Ransom.Gen Activity 22

    Posted Jul 25, 2018 04:57 PM

    Same. Nothing get pick up from scanning. Ransom.Gen Activity 22 seem to flight under SEP's radar.



  • 9.  RE: Attack: Ransom.Gen Activity 22

    Posted Jul 31, 2018 10:04 AM

    I have the same issue beside "Attack: Ransom.Gen Activity 20"...and nothing detected even after full scan.



  • 10.  RE: Attack: Ransom.Gen Activity 22

    Posted Aug 06, 2018 06:56 AM

    Same here. Attacking Mails with:

    Attack: Ransom.Gen Activity 22

    arrives every 16 minutes. The Network traffic (especially shares) is blocked. Fullscan with Symantec and other AV's dont show any malware.

    Regards



  • 11.  RE: Attack: Ransom.Gen Activity 22

    Posted Aug 16, 2018 07:21 AM

    just understand, here your machine is not infected but some other machine is infected which is trying IPS attack to your machine. Your SEP client is blocking attacks and a notification is generated in your machine. 

    Now to get original source machine of attack you can  refer either of client or server  logs for details 

    for detailed steps pls refer https://www.symantec.com/connect/articles/trace-smb-double-pulsar-attack-source-machines 



  • 12.  RE: Attack: Ransom.Gen Activity 22

    Posted Dec 06, 2018 01:00 PM

    After recovering from a recent ransomware attack ourselves, we continued to get the Ransom.Gen Activity 22 message from some of our users. The attack originally came through a standard user profile so when we originally restored from backup, there were some nested folders which appeared to be unaffected.

    Example - The files within (Share)\Employees\John were not affected due to the elevated privileges for the John Folder. When I had restored, I left the John folder and the Employees folder, but deleted/restored all of the other file folders which contained files that had been encrypted.

    Suspected solution: I think I was able to resolve the issue on our end by creating a new "Employees" folder, moving everything to the new folder and deleting the old. Try to replace any folders which may have been affected in addition to files.

    Alternate solution: During the process, I also ended up reassigning permission values to all of the shared folders. This may have inadvertantly fixed the issue on our end.

    I hope this helps someone else. If someone finds that they can reproduce these results, please respond. Thanks!