Proplem with suricate after upgarde from 2.3.140 to 2.3.160

[tswiderski1]

After updating the suricata, she started to win a lot of alerts. It detects various problems even in local traffic, e.g.
MALWARE-CNC FF-RAT outbound connection attempt
PUA-P2P WinNY connection attempt
NETBIOS SMB write_andx overflow attempt
OS-WINDOWS PGM on the overflow attempt list
SERVER-OTHER Cisco ASA SCPS command injection attempt
....
and 100 others

I checked with other tools the traffic is not infected.
Suricata detects several thousand alerts per minute. As I checked, it looks like the traffic is infected. The alerts appeared exactly after the OS update was completed.

What could be the cause?
How can I run a previous version of Suricata?
How do I disable Suricata until the problem is resolved?

[dougburks]

I suspect that you're using a Snort ruleset and its Shared Object rules are firing since they are not fully compatible with Suricata. If that's the case, you'll want to disable the Shared Object rules as shown here:
https://docs.securityonion.net/en/2.3/rules.html#snort-registered

[tswiderski1]

I came to the same conclusion. I just wonder why there was no such problem before the update. I suppose before the update, Surricata wasn't working properly, although it did log various events at times.