CuraSec

tag: C2 · 5 items

2026-08-19 · The Hacker News · source ↗ #malware#microsoft-365#c2
  • Engineer — Learn: No exploitation signals or patch action required, but this technique highlights the risk of trusting M365 egress unconditionally; review whether SharePoint/Teams API access from non-user contexts is logged and anomaly-monitored in your environment.
  • SOC/IR — Plan: TWINLOOT’s C2-over-SharePoint-Online pattern blends into legitimate M365 traffic — build or tune detections for unusual SharePoint file polling cadence and Teams API calls from non-interactive service contexts to catch implants using this framework.
  • Leader — Learn: Newly documented implant class that weaponizes trusted M365 services, useful context for future conversations about M365 security controls and monitoring investment, but no confirmed active campaigns require immediate leadership action.
2026-08-04 · Unit 42 · source ↗ #malware#c2#detection
  • Engineer — Plan: Audit egress firewall rules to block or alert on outbound connections to raw IPs (not resolved via internal DNS); this is a concrete hardening step supported by the finding.
  • SOC/IR — Plan: Build or tune detections for outbound traffic to bare IP addresses without preceding DNS resolution — this pattern is a high-signal C2 indicator worth adding to your SIEM hunting queries.
  • Leader — Skip
2026-07-27 · The Hacker News · source ↗ #apt#c2#malware
  • Engineer — Skip
  • SOC/IR — Learn: New malware cluster (TELESHIM, MIXEDKEY, BINDCLOAK) using Telegram as C2 channel is worth tracking for detection coverage, but no IOCs or ATT&CK mappings are provided in the current reporting — revisit when Zscaler publishes technical indicators.
  • Leader — Learn: East Asian threat actor targeting Middle East government entities with novel tooling; relevant for sector awareness but no vendor exposure or regulatory trigger for a US/global enterprise leader.
2026-07-21 · BleepingComputer · source ↗ #malware#microsoft-365#c2
  • Engineer — Learn: Novel living-off-the-land C2 technique abusing legitimate Microsoft Graph calendar APIs to blend into normal M365 traffic; no patch exists but worth reviewing M365 conditional-access and app-permission scopes to limit blast radius of compromised accounts.
  • SOC/IR — Plan: Build or tune detection for anomalous Graph API calendar activity (unexpected event creation, unusual read patterns from non-user agents) in M365 audit logs; no published IOCs yet, but the TTP is concrete enough to start a detection rule in Sentinel or Elastic against Graph audit data.
  • Leader — Learn: Illustrates how attackers leverage licensed SaaS infrastructure to evade network-level controls; useful context for future budget conversations around M365 audit-log retention and cloud SIEM coverage, but no immediate leadership action required.
2026-07-10 · The Hacker News · source ↗ #rat#threat-actor#c2
  • Engineer — Learn: gRPC-based C2 may evade TLS inspection tuned for HTTP/2 REST traffic; review whether your egress controls decode and inspect gRPC streams.
  • SOC/IR — Plan: Build or tune detections for outbound gRPC streaming to novel external endpoints; Silver Fox distributes via SEO-poisoned counterfeit installers, so hunt for unexpected Rust-compiled binaries in user-facing application paths.
  • Leader — Learn: Adds to the picture of China-linked actors targeting enterprise software supply chains via SEO poisoning; useful context for board-level threat landscape briefings but no immediate action required.