A researcher demonstrated that attackers can take over a company’s branded QR-code subdomain (e.g., qr.company.com) if the company stops using a QR vendor but forgets to remove the DNS record. Anyone scanning a legitimate printed QR code can then be redirected to an attacker-controlled website, enabling phishing or fraud while the link still looks like the real company domain.
How the attack worked
A researcher demonstrated that branded QR-code subdomains, such as qr.company.com, can be hijacked if a company stops using a QR vendor but forgets to remove the DNS CNAME record pointing at that vendor's platform. Because the record still exists, an attacker can claim the abandoned subdomain through the vendor's platform and set a new redirect destination. Anyone who scans an already-printed QR code, whether on packaging or a conference stand, is then sent to attacker-controlled content while the link still displays the company's own domain.
Why it succeeded
The root issue was a verification gap: the vendor platform only checked that a DNS record existed, not who actually owned or controlled the subdomain behind it. This meant any account holder on the platform could claim a subdomain that was still pointing at it but was no longer actively registered by the original company. The researcher noted the entire takeover process takes under a minute. On top of that, people tend to trust QR codes more than email links, especially when the resulting page shows a familiar corporate domain, making the redirect far less likely to be questioned.
What to watch for
- QR codes that lead to unexpected pages, or that suddenly ask for credentials, payment, or downloads unrelated to the original context
- Branded subdomains whose page content or layout looks inconsistent with known official pages
- QR codes tied to old campaigns, packaging, or printed materials that can no longer be updated or recalled
- Internal DNS records for third-party QR or marketing platforms that no one currently owns
Building resistance
Organizations should treat QR codes with the same scrutiny as links: verify destinations and be cautious of unexpected login or payment prompts, even when the domain looks branded. IT and web teams should periodically audit DNS records after campaigns end or vendors are discontinued, removing stale CNAME entries that still point to third-party platforms. Where custom domains are used with SaaS platforms, ownership should be verified using a unique token published in a TXT record rather than relying on the mere existence of a DNS record. Because printed QR codes can't be recalled the way software can be updated, sensitive actions such as logins or payments should not depend solely on a scanned link, and teams should prefer short-lived or centrally managed redirects for any QR campaign tied to physical materials.
Key findings
- Attackers can claim a company’s branded QR subdomain on a QR-code vendor platform if the company left a stale DNS CNAME pointing at the vendor.
- This can redirect scans of already-printed “genuine” QR codes to an attacker-controlled destination while still showing a legitimate corporate domain.
- The vendor check described verifies only that the DNS record exists, not that the requester controls/owns the subdomain.
- The issue may affect many organizations: the researcher said he found “hundreds of vulnerable companies across manufacturing, healthcare, financial services and technology.”
- Mitigation includes removing stale DNS records and using a TXT-record ownership token to prove control of the domain.
Who’s being targeted
- Commonly targeted roles: All employees, Marketing, IT, Web/Digital teams, Event staff.
- Affected industries: Manufacturing, Healthcare, Financial services, Technology.
- Attack channels: physical, website.
- Impersonated: Victim company’s branded QR link (company-owned subdomain), QR-code vendor custom domain feature (claiming an existing subdomain).
Red flags to watch for
- The QR code leads to an unexpected page or asks for credentials/payment unrelated to the context.
- The company uses a branded subdomain, but the content/layout looks off or differs from known official pages.
- The QR code is from an old campaign or printed material that can’t be updated or recalled.
- A custom-domain claim process that does not require a unique verification token (TXT record).
- Old DNS records for prior vendors/campaigns still present with no internal owner.
- Unexpected ownership changes or redirects on a branded QR subdomain.
Frequently asked questions
How can a legitimate QR code be hijacked?
If a company stops using a QR-code vendor but leaves the DNS record pointing to that vendor's platform, an attacker can claim the abandoned subdomain and redirect any scan of an already-printed code to a destination they control.
Why didn't the QR platform prevent this?
The platform only checked that the DNS record existed, not who actually controlled or owned the subdomain, which allowed any account holder to claim it.
How widespread is this issue?
The researcher reported finding hundreds of vulnerable companies across manufacturing, healthcare, financial services and technology.
How can organizations prevent this?
They should remove stale DNS records for unused vendor integrations and require a unique ownership token published in a TXT record before a custom domain can be claimed.
Read the video transcript
You know those QR codes on our packaging and conference stands? Those can be hijacked even if they still show our real domain. A researcher showed he could claim abandoned QR subdomains like 'qr.company.com' on a vendor’s platform, then send every scan to his own site, while phones still displayed the real corporate domain. Someone scans an old campaign QR, sees 'qr.company.com', but lands on a page asking for login or payment that doesn’t match our usual look. People who distrust email links rarely question a code on packaging or a conference stand. Here’s the move: if a QR to our domain ever asks for credentials or payment, stop and report it to security, include a screenshot of the page and the 'qr.ourcompany.com' address your phone shows.