Skip to content
skopnix
← Sigma detections

Sigma · Actor indicator sweep

TeamPCP IP indicators

severity
high
confidence
70/100
generated
19 Nov 2026
Linked actors
TeamPCP

1 IP indicator skopnix attributes to TeamPCP, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).

False-positive notes

1 indicator. Evidence: 1 by one feed with confidence >= 75 (lowest 76). Listed by 1 independent source in all. Newest feed sighting 2026-11-19, oldest 2026-11-19 (a live actor sweep accepts at most 90 days). Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists. Re-validate against last_seen before blocking: infrastructure is re-assigned.

References

title: Skopnix - TeamPCP IP indicatorsid: 2ae2566a-a6ba-5957-b3c3-733fe217cd6dstatus: experimentaldescription: 1 IP indicator skopnix attributes to TeamPCP, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).references:  - https://skopnix.com/actors/teampcpauthor: skopnixdate: '2026-11-19'tags:  - attack.command-and-control  - attack.t1071logsource:  category: firewalldetection:  selection:    dst_ip:      - 45.148.10.212  condition: selectionfalsepositives:  - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: high

skopnix-sigma-actor-teampcp-ip-3abc6df0.yml

How to deploy on Sigma

Step 1
Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
Step 2
Run it as a hunt first: every rule ships as status experimental.
Step 3
Promote to an alert once a week of results is clean on your data.
Check
The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.