# False positive 2035595 - zgRAT / PureRAT confusion

**URL:** <https://community.emergingthreats.net/t/false-positive-2035595-zgrat-purerat-confusion/3393>\
**Category:** Rule Signatures\
**Tags:** false-positives\
**Created:** [July 22, 2026, 5:07pm UTC](https://community.emergingthreats.net/t/false-positive-2035595-zgrat-purerat-confusion/3393 "2026-07-22T17:07:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![erik4711](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erik4711](https://community.emergingthreats.net/u/erik4711)\
**Post date:** [August 9, 2026, 8:19pm UTC](https://community.emergingthreats.net/t/false-positive-2035595-zgrat-purerat-confusion/3393/4 "2026-08-09T20:19:56Z")

</div>

Thank you for the update!

Clarification: The sandbox links in my original post are examples of PureRAT samples that trigger the sid 2035595 zgRAT signature. As an example, the following C2 servers can be found in the JoeSandbox PCAP:

- `91.219.238[.]82:8541` = XWorm
- `91.219.238[.]82:56001` = **PureRAT** over TLS
- `91.219.238[.]166:8045` = DCRat over TLS
- `91.219.238[.]166:8443` = PureLogs over TLS

The zgRAT signature 2035595 only triggers on the PureRAT traffic in the JoeSandbox PCAP. I’ve never seen that signature trigger on C2 traffic from any of the other malware families from PureCoder (such as PureLogs). That’s one of the reasons why I propose the name change from zgRAT to PureRAT for this signature.

I have now verified that I also sometimes see sid 2035595 trigger on AsyncRAT traffic.

---

_[View the full topic](https://community.emergingthreats.net/t/false-positive-2035595-zgrat-purerat-confusion/3393)._
