PureRAT
94 addresses convicted as PureRAT remote-access trojan controllers — 94 still listed, 0 archived. Observed from 2026-08-23.
Detection packs
Rules for the 94 still-listed addresses on this page, regenerated as the archive updates; archived episodes are omitted, and a rule can lag a withdrawal by up to five minutes. Suricata rules are rev:2 — alert tcp on address and port, alert tls where a full certificate fingerprint is published — and carry the archive's own episode ids as sids, so packs load beside each other and beside any per-host file. YARA packs are hash matches only: this site holds no file bytes.
About
A .NET remote-access trojan sold as a subscription rather than published, and delivered by the same vendor's loader. What this corpus records is the CONTROLLER — the operator's listener, not an infected machine. Its listeners cluster tightly on 56001-56004 alongside 443, which is a usable hunting observable in its own right. Re-labelled by the upstream in place: 1 host earlier labelled Quasar. The archive keeps only the most recent earlier label per episode. Recently first observed in AS63119 on 2026-09-10 (1 host); AS203446 on 2026-09-08 (1 host); AS36352 on 2026-09-08 (1 host); AS400897 on 2026-09-08 (1 host) — networks this family had not appeared in before, as seen by this archive. Upstream population estimate: hosts of this family observed moving toward AS399979 on 2026-09-14 (fewer than 10 hosts); toward AS16509 on 2026-09-13 (fewer than 10 hosts); toward AS58212 on 2026-09-10 (fewer than 10 hosts); toward AS45753 on 2026-09-08 (fewer than 10 hosts) — the upstream scanner's estimate from a passive search population, not this archive's observation, and shown only for networks where this archive holds at least one host of this family.
Ports
Addresses
Ordered by when this archive first recorded them, newest first — a stable ordering, so a page holds the same addresses tomorrow. Archived addresses are included and marked; they are the majority of this corpus over time.
Listed in error?
These pages are generated from automated scanning and are publicly available. Write to support@publicmosaic.com — see abuse & takedown, or opt-out to exclude a network range from scanning.