Loading malware…
bcs_server is a Sandworm Team tool used to create an internal proxy server that redirects traffic from adversary-controlled command-and-control infrastructure to internal servers. The reported purpose is to reach internal systems that may not be directly connected to the internet but are locally interconnected. High-confidence reporting in the provided content attributes this proxying capability to Sandworm Team and describes its role as an internal traffic relay/pivoting mechanism. No additional infection vector, platform details, industries targeted, or specific indicators of compromise are provided in the content.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
Sandworm Team's BCS-server tool can create an internal proxy server to redirect traffic from the adversary-controlled C2 to internal servers.
1 distinct technique documented for this family, organized by ATT&CK tactic.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Tool that creates an internal proxy server to redirect C2 traffic to internal-only hosts.
Tool that creates an internal proxy server to redirect traffic from external C2 to internal-only servers.
Tool that creates an internal proxy server to redirect C2 traffic to internal-only servers.
Tool that creates an internal proxy server to redirect C2 traffic to internal-only servers.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.