<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/rss-style.xsl" type="text/xsl"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	     xmlns:dc="http://purl.org/dc/elements/1.1/"
	   xmlns:atom="http://www.w3.org/2005/Atom"
	     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	  xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>
<channel>
	<title>hijacking &#8211; Terence Eden’s Blog</title>
	<atom:link href="https://shkspr.mobi/blog/tag/hijacking/feed/" rel="self" type="application/rss+xml" />
	<link>https://shkspr.mobi/blog</link>
	<description>Regular nonsense about tech and its effects 🙃</description>
	<lastBuildDate>Mon, 25 Aug 2025 12:59:38 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://shkspr.mobi/blog/wp-content/uploads/2023/07/cropped-avatar-32x32.jpeg</url>
	<title>hijacking &#8211; Terence Eden’s Blog</title>
	<link>https://shkspr.mobi/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title><![CDATA[How To Prevent QR Hijacking]]></title>
		<link>https://shkspr.mobi/blog/2011/12/how-to-prevent-qr-hijacking/</link>
					<comments>https://shkspr.mobi/blog/2011/12/how-to-prevent-qr-hijacking/#comments</comments>
				<dc:creator><![CDATA[@edent]]></dc:creator>
		<pubDate>Thu, 01 Dec 2011 16:25:51 +0000</pubDate>
				<category><![CDATA[qr]]></category>
		<category><![CDATA[hijacking]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">http://shkspr.mobi/blog/?p=4883</guid>

					<description><![CDATA[QR-jacking is the act of covering up a QR code and replacing it with an alternative - often malicious - code.  Your carefully crafted code could be replaced by one which...       Points to a rival&#039;s site.     Calls a premium rate phone number.     Redirects the user to a site which EXPOSES THE TRUTH BEHIND...     Goes to a non-legitimate site which asks for credit card / personal details.    …]]></description>
										<content:encoded><![CDATA[<p>QR-jacking is the act of covering up a QR code and replacing it with an alternative - often malicious - code.</p>

<p>Your carefully crafted code could be replaced by one which...</p>

<ul>
    <li>Points to a rival's site.</li>
    <li>Calls a premium rate phone number.</li>
    <li>Redirects the user to a site which EXPOSES THE TRUTH BEHIND...</li>
    <li>Goes to a non-legitimate site which asks for credit card / personal details.</li>
    <li>Downloads a virus or other form of malicious content.</li>
</ul>

<p>It's a real threat - thankfully it's usually easy to spot.  Especially in this case...
<a href="http://twitpic.com/7lieow"><img src="https://shkspr.mobi/blog/wp-content/uploads/2011/12/QR-Jacking.jpg" alt="QR Jacking" title="QR Jacking" width="600" height="402" class="aligncenter size-full wp-image-4884"></a></p>

<p>In the above image, it should be fairly obvious to anyone that the QR code has been replaced.</p>

<h2 id="combating-qr-hijacking"><a href="https://shkspr.mobi/blog/2011/12/how-to-prevent-qr-hijacking/#combating-qr-hijacking">Combating QR Hijacking</a></h2>

<p>There are some practical actions you can take to make sure that your code isn't hijacked.</p>

<ol>
    <li>Say where your code will go.  In your call to action say something like "Scan for our mobile site" that way, it should be obvious that a code which tries to call a premium rate number is fraudulent.</li>
    <li>Don't use short URLs. How can a customer tell if <a href="https://shkspr.mobi/blog/2011/04/dear-nokia/">bit.ly/CYRWP</a> goes to your site or to a rivals? Always use your domain name in your QR codes.</li>
    <li>Place a logo in your QR codes. It's not foolproof, but it means the hijacker has to work harder to look legitimate.</li>
    <li>Use a light background colour for your code. It will mean the hijacker has to print on more expensive coloured paper and it is less likely to look like a seamless replacement.</li>
    <li>Track down hijackers. If a your code is being redirected, try to track down those responsible.</li>
</ol>

<h2 id="finding-joachim-schmid"><a href="https://shkspr.mobi/blog/2011/12/how-to-prevent-qr-hijacking/#finding-joachim-schmid">Finding Joachim Schmid</a></h2>

<p>I am fairly confident that the above inept defacement was by Joachim Schmid.</p>

<ul>
<li>The above photo was taken at Olympia in London.  The same defacement is recorded on the <a href="https://web.archive.org/web/20120202142541/http://nineerrors.files.wordpress.com/2011/11/qr146.jpg">Nine Errors blog</a>, which appears to be <a href="https://www.lumpenfotografie.de/2011/04/29/nine-errors-2010/">run by Schmid</a>.</li>
<li>The photo on the Nine Errors blog was taken on November the 18th, according to the EXIF data.</li>
<li>Schmid was <a href="https://www.lumpenfotografie.de/2011/11/16/talk-in-london-2/">presenting his work</a> at Olympia on November 18th.</li>
</ul>

<p>The Nine Errors project is a slightly odd attempt by <a href="http://schmid.wordpress.com/">Joachim Schmid</a> to "intervene" and <a href="https://web.archive.org/web/20110806123410/http://nineerrors.wordpress.com/interventions/">redirect QR codes to error pages</a>.</p>

<h2 id="need-help"><a href="https://shkspr.mobi/blog/2011/12/how-to-prevent-qr-hijacking/#need-help">Need Help?</a></h2>

<p>Want some bespoke QR advice? <a href="https://edent.tel/">Give me a call</a>.</p>
<img src="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/info/okgo.php?ID=4883&HTTP_REFERER=RSS" alt="" width="1" height="1" loading="eager">]]></content:encoded>
					
					<wfw:commentRss>https://shkspr.mobi/blog/2011/12/how-to-prevent-qr-hijacking/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
	</channel>
</rss>
