<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/css" media="screen" href="http://s2.wp.com/wp-content/themes/vip/newyorkobserver/stylesheets/rss.css"?>
<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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Betabeat &#187; We Got the New York Times Email Spam. Feeling Special</title>
	<atom:link href="http://betabeat.com/2011/12/new-york-times-spam-email-hacked/feed/" rel="self" type="application/rss+xml" />
	<link>http://betabeat.com</link>
	<description>Just another WordPress.com site</description>
	<lastBuildDate>Sun, 19 May 2013 04:58:29 +0000</lastBuildDate>
	<language></language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='betabeat.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Betabeat &#187; We Got the New York Times Email Spam. Feeling Special</title>
		<link>http://betabeat.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://betabeat.com/osd.xml" title="Betabeat" />
	<atom:link rel='hub' href='http://betabeat.com/?pushpress=hub'/>
		<item>
				
		<title>We Got the New York Times Email Spam. Feeling Special</title>

		<comments>http://betabeat.com/2011/12/new-york-times-spam-email-hacked/#comments</comments>
		<pubDate>Wed, 28 Dec 2011 14:00:09 -0400</pubDate>
					<link>http://betabeat.com/2011/12/new-york-times-spam-email-hacked/</link>
			<dc:creator>Ben Popper</dc:creator>
				
		<guid isPermaLink="false">http://www.betabeat.com/?p=25387</guid>
		<description><![CDATA[<p><div id="attachment_25391" class="wp-caption aligncenter" style="width: 575px"><img class="size-full wp-image-25391" title="nyt spam" src="http://nyobetabeat.files.wordpress.com/2011/12/nyt-spam.jpg" alt="" width="565" height="230" /><p class="wp-caption-text">Holiday Mischief?</p></div></p>
<p>UPDATE: The email was from the <em>NYT,</em> but went to the wrong list, <a href="https://twitter.com/#!/brianstelter/status/152124533464240128/embed">according to<em> Times</em> staffers</a><em>.</em></p>
<p>We just got the email which the <em>New York Times</em> PR is saying "looks like spam." It arrived from the succinct address: nytimes@email.newyorktimes.com</p>
<p>I am not a home, digital, tablet or anything subscriber. But apparently:</p>
<blockquote><p><em>Our records indicate that you recently requested to cancel your home delivery subscription. Please keep in mind when your delivery service ends, you will no longer have unlimited access to NYTimes.com and our NYTimes apps. </em></p>
<p><em>We do hope you’ll reconsider. </em></p>
<p><em>As a valued Times reader we invite you to continue your current subscription at an exclusive rate of 50% off for 16 weeks. This is a limited-time offer and will no longer be valid once your current subscription ends.* </em></p>
<p><em>Continue your subscription and you’ll keep your free, unlimited digital access, a benefit available only for our home delivery subscribers. You’ll receive unlimited access to NYTimes.com on any device, full access to our smartphone and iPad<sup>®</sup> apps, plus you can now share your unlimited access with a family member.<sup>†</sup> </em></p>
<p><em>To continue your subscription call <a href="tel:1-877-698-0025" target="_blank">1-877-698-0025</a> and mention code 38H9H (Monday–Friday, 8:30 a.m. to 8:30 p.m.; Saturday, 9 a.m. to 3 p.m. E.D.T.).</em></p></blockquote>
<p><em>New York Observer</em> editor Aaron Gell called the number in this email—not confirmed to be a <em>New York Times</em> number, but possibly a call center that routes calls regarding <em>Times</em> distribution—and got a voicemail saying call volume is too high to process. Betabeat's repeated calls to the number were met with a busy signal.</p>
<p>This spam went far and wide (and is now <a href="https://gist.github.com/1529231">on Github</a>). It appears to have gone out to the <em>Times's</em> registered users' list; one user <a href="https://twitter.com/#!/lexfri/status/152100816004710401">noted that the message arrived in an inbox he only uses for the </a><em><a href="https://twitter.com/#!/lexfri/status/152100816004710401">Times</a>: </em>nytimes [at) thefriedmans.net.</p>
<p>UPDATE: <a href="http://twitter.com/nytprguy">@NYTPRGUY</a> is passing the buck. Via Twitter, "We are investigating emails, please contact Eileen Murphy for full comment: eileen.murphy@nytimes.com."</p>
<blockquote class="twitter-tweet"><p>If you received an email today about canceling your NYT subscription, ignore it. It's not from us.</p>
<p>— The New York Times (@nytimes) <a href="https://twitter.com/nytimes/status/152101947523088384">December 28, 2011</a></p></blockquote>
<p><script src="//platform.twitter.com/widgets.js"></script> Two folks on Twitter are now saying the email can be traced back to Epsilon, a marketing firm.</p>
<p><div id="attachment_25394" class="wp-caption aligncenter" style="width: 608px"><img class="size-full wp-image-25394" title="nyt epsilon" src="http://nyobetabeat.files.wordpress.com/2011/12/nyt-epsilon.jpg" alt="" width="598" height="272" /><p class="wp-caption-text">via Twitter</p></div></p>
<p>Oddly, the <a href="http://homedelivery.nytimes.com/maintenance/index.html"><em>Times</em>'s home delivery page is down for routine maintenance</a> as of 2:24 p.m.  <img class="alignnone size-full wp-image-25400" style="margin-top: 5px; margin-bottom: 5px; margin-left: 10px; margin-right: 10px;" title="nyt maintenance" src="http://nyobetabeat.files.wordpress.com/2011/12/nyt-maintenance.png" alt="" width="526" height="246" /></p>
<p>UPDATE: Epsilon spokesperson Jessica Simon says, "This is the first I've heard of it. Let me talk with our email group and get back to you."  UPDATE: Oops.</p>
<blockquote class="twitter-tweet"><p>
Today's subscriber email wasn't a hack; it WAS sent by the NYT. RT @<a href="https://twitter.com/amychozick">amychozick</a>: Should've gone to appx 300 people &amp; went to over 8 mil.</p>
<p>— Brian Stelter (@brianstelter) <a href="https://twitter.com/brianstelter/status/152124533464240128">December 28, 2011</a>
</p></blockquote>
<p><script src="//platform.twitter.com/widgets.js"></script></p>
]]></description>
		<content:encoded><![CDATA[<p><div id="attachment_25391" class="wp-caption aligncenter" style="width: 575px"><img class="size-full wp-image-25391" title="nyt spam" src="http://nyobetabeat.files.wordpress.com/2011/12/nyt-spam.jpg" alt="" width="565" height="230" /><p class="wp-caption-text">Holiday Mischief?</p></div></p>
<p>UPDATE: The email was from the <em>NYT,</em> but went to the wrong list, <a href="https://twitter.com/#!/brianstelter/status/152124533464240128/embed">according to<em> Times</em> staffers</a><em>.</em></p>
<p>We just got the email which the <em>New York Times</em> PR is saying "looks like spam." It arrived from the succinct address: nytimes@email.newyorktimes.com</p>
<p>I am not a home, digital, tablet or anything subscriber. But apparently:</p>
<blockquote><p><em>Our records indicate that you recently requested to cancel your home delivery subscription. Please keep in mind when your delivery service ends, you will no longer have unlimited access to NYTimes.com and our NYTimes apps. </em></p>
<p><em>We do hope you’ll reconsider. </em></p>
<p><em>As a valued Times reader we invite you to continue your current subscription at an exclusive rate of 50% off for 16 weeks. This is a limited-time offer and will no longer be valid once your current subscription ends.* </em></p>
<p><em>Continue your subscription and you’ll keep your free, unlimited digital access, a benefit available only for our home delivery subscribers. You’ll receive unlimited access to NYTimes.com on any device, full access to our smartphone and iPad<sup>®</sup> apps, plus you can now share your unlimited access with a family member.<sup>†</sup> </em></p>
<p><em>To continue your subscription call <a href="tel:1-877-698-0025" target="_blank">1-877-698-0025</a> and mention code 38H9H (Monday–Friday, 8:30 a.m. to 8:30 p.m.; Saturday, 9 a.m. to 3 p.m. E.D.T.).</em></p></blockquote>
<p><em>New York Observer</em> editor Aaron Gell called the number in this email—not confirmed to be a <em>New York Times</em> number, but possibly a call center that routes calls regarding <em>Times</em> distribution—and got a voicemail saying call volume is too high to process. Betabeat's repeated calls to the number were met with a busy signal.</p>
<p>This spam went far and wide (and is now <a href="https://gist.github.com/1529231">on Github</a>). It appears to have gone out to the <em>Times's</em> registered users' list; one user <a href="https://twitter.com/#!/lexfri/status/152100816004710401">noted that the message arrived in an inbox he only uses for the </a><em><a href="https://twitter.com/#!/lexfri/status/152100816004710401">Times</a>: </em>nytimes [at) thefriedmans.net.</p>
<p>UPDATE: <a href="http://twitter.com/nytprguy">@NYTPRGUY</a> is passing the buck. Via Twitter, "We are investigating emails, please contact Eileen Murphy for full comment: eileen.murphy@nytimes.com."</p>
<blockquote class="twitter-tweet"><p>If you received an email today about canceling your NYT subscription, ignore it. It's not from us.</p>
<p>— The New York Times (@nytimes) <a href="https://twitter.com/nytimes/status/152101947523088384">December 28, 2011</a></p></blockquote>
<p><script src="//platform.twitter.com/widgets.js"></script> Two folks on Twitter are now saying the email can be traced back to Epsilon, a marketing firm.</p>
<p><div id="attachment_25394" class="wp-caption aligncenter" style="width: 608px"><img class="size-full wp-image-25394" title="nyt epsilon" src="http://nyobetabeat.files.wordpress.com/2011/12/nyt-epsilon.jpg" alt="" width="598" height="272" /><p class="wp-caption-text">via Twitter</p></div></p>
<p>Oddly, the <a href="http://homedelivery.nytimes.com/maintenance/index.html"><em>Times</em>'s home delivery page is down for routine maintenance</a> as of 2:24 p.m.  <img class="alignnone size-full wp-image-25400" style="margin-top: 5px; margin-bottom: 5px; margin-left: 10px; margin-right: 10px;" title="nyt maintenance" src="http://nyobetabeat.files.wordpress.com/2011/12/nyt-maintenance.png" alt="" width="526" height="246" /></p>
<p>UPDATE: Epsilon spokesperson Jessica Simon says, "This is the first I've heard of it. Let me talk with our email group and get back to you."  UPDATE: Oops.</p>
<blockquote class="twitter-tweet"><p>
Today's subscriber email wasn't a hack; it WAS sent by the NYT. RT @<a href="https://twitter.com/amychozick">amychozick</a>: Should've gone to appx 300 people &amp; went to over 8 mil.</p>
<p>— Brian Stelter (@brianstelter) <a href="https://twitter.com/brianstelter/status/152124533464240128">December 28, 2011</a>
</p></blockquote>
<p><script src="//platform.twitter.com/widgets.js"></script></p>
]]></content:encoded>
		<wfw:commentRss>http://betabeat.com/2011/12/new-york-times-spam-email-hacked/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
	
		<media:content url="http://2.gravatar.com/avatar/becf95fa833b8aeb13f7720732bd6dc6?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jhanasobserver</media:title>
		</media:content>

		<media:content url="http://nyobetabeat.files.wordpress.com/2011/12/nyt-spam.jpg" medium="image">
			<media:title type="html">nyt spam</media:title>
		</media:content>

		<media:content url="http://nyobetabeat.files.wordpress.com/2011/12/nyt-epsilon.jpg" medium="image">
			<media:title type="html">nyt epsilon</media:title>
		</media:content>

		<media:content url="http://nyobetabeat.files.wordpress.com/2011/12/nyt-maintenance.png" medium="image">
			<media:title type="html">nyt maintenance</media:title>
		</media:content>
	</item>
	</channel>
</rss>
