Six-Month Review Finds C2 Fingerprints Outlast YouTube DMCA Phishing Indicators

· Original article ↗

Summary

A six-month review found IP, CSS and favicon pivots from a YouTube DMCA phishing campaign quickly went stale, while C2 banner/header hashes and newer title-tag and redirect patterns exposed related infrastructure.

Key points

  • IP, CSS-class and favicon pivots from the November 2025 campaign produced little new activity over time.
  • C2 banner and response-header hashes continued to reveal new infrastructure during the six-month review.
  • A title-tag pivot from dmca-notification[.]info matched hundreds of domains observed between February and May 2026; only the original domain was publicly flagged as malicious in Validin.
  • The credential-harvesting domain blacklivesmattergood4[.]com redirected to /youtube/main/; searching for that pattern identified nearly 100 other domains.
  • The April 2026 campaign used a personalized fake Google login with a Browser-in-the-Browser technique, unlike the earlier campaign's malware-download lure.
  • The authors demonstrate using historical DNS, response fingerprints, title tags and redirect patterns to expand point-in-time indicators into potentially related infrastructure.

Article Details

Attack Vectors
  • Fake YouTube DMCA copyright notices lured creators to malicious sites.
  • A later campaign used a personalized fake Google login with a Browser-in-the-Browser presentation.
  • A credential-harvesting domain redirected visitors to /youtube/main/.
Defensive Notes
  • The article reports that historical IP and simple class or favicon hash pivots quickly became stale; C2 banner and header fingerprints continued to surface related infrastructure.
  • Use historical DNS, response-header fingerprints, title tags, and redirect patterns as complementary pivots when investigating related domains.
  • Treat domains discovered through shared fingerprints as related leads: the article notes that only the original domain in the title-tag cluster had a public malicious flag in Validin.

Indicators of compromise

TypeIndicatorContext
DOMAINalphazero1-endscape[.]ccDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINblacklivesmattergood4[.]comDomain reported as a credential-harvesting endpoint; the phishing lure communicated with it.
DOMAINdmca-notification[.]infoDomain reported as the primary phishing site in the newer YouTube DMCA campaign.
DOMAINdmca-takedown[.]infoNamed as an example of a domain related to the YouTube DMCA phishing infrastructure.
DOMAINdomain-monitoring[.]ccDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINfileless-storage-s3[.]ccDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINhandle-me-sv1[.]comDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINhardware-office[.]ccDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINhealth-smooth-eu3[.]comDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINholiday-updateservice[.]comDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINmemory-protection-layer1[.]ccDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINmemory-protection-layer2[.]ccDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINmy-smart-house1[.]comDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINvvork-space[.]comDomain surfaced through response-header fingerprinting associated with C2 domains.
DOMAINyoutube-dmca[.]cfdNamed as an example of a domain related to the YouTube DMCA phishing infrastructure.
IPV4101[.]99[.]89[.]94Historical DNS pivot associated with infrastructure from the earlier reported phishing campaign.
IPV4101[.]99[.]92[.]246Historical DNS pivot associated with infrastructure from the earlier reported phishing campaign.
IPV4176[.]46[.]152[.]11IP address reported to have responded with the banner hash associated with C2 infrastructure.
IPV4193[.]23[.]199[.]125IP address reported to have responded with the banner hash associated with C2 infrastructure.
IPV445[.]156[.]87[.]34IP address reported to have responded with the banner hash associated with C2 infrastructure.
IPV446[.]151[.]182[.]8IP address reported to have responded with the banner hash associated with C2 infrastructure.
IPV45[.]188[.]190[.]160IP address reported to have responded with the banner hash associated with C2 infrastructure.
MD55dab1fa5f7d42e5eca2385ce3dad1f03Banner fingerprint associated with IP addresses used for C2 in the original malware analysis.

MITRE ATT&CK

People

Products

Tools

Related Articles