<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>The Merchant Account Blog</title>
	
	<link>http://www.merchantaccountblog.com</link>
	<description>Merchant Accounts, Ecommerce, Processing Equipment</description>
	<lastBuildDate>Sat, 04 Jul 2009 20:57:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/TheMerchantAccountBlog" type="application/rss+xml" /><item>
		<title>Authorize.net goes down</title>
		<link>http://www.merchantaccountblog.com/767/authorize-net-goes-down</link>
		<comments>http://www.merchantaccountblog.com/767/authorize-net-goes-down#comments</comments>
		<pubDate>Fri, 03 Jul 2009 16:02:51 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=767</guid>
		<description><![CDATA[Authnet suffered an outage this morning. Current rumors suggest that it was due to a fire at a data-center, which subsequently destroyed the backup generators from the sprinklers.
Authorize.net is currently the largest payment gateway in the world. This is affecting millions of websites right now. To my knowledge this is the first major outage since [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://mashable.com/2009/07/03/authorize-net-down/">Authnet suffered an outage this morning</a>. Current rumors suggest that it was due to a fire at a data-center, which subsequently destroyed the backup generators from the sprinklers.</p>
<p>Authorize.net is currently the largest payment gateway in the world. This is affecting millions of websites right now. To my knowledge this is the first major outage since <a href="http://news.netcraft.com/archives/2004/09/20/ddos_attacks_target_authorizenet.html">the DDOS attack</a> they suffered several years ago. </p>
<p>A casualty of this magnitude has the ability to permanently damage / destroy this company&#8217;s trust and reputation.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/767/authorize-net-goes-down/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PA-DSS, and you thought PCI was a mess!</title>
		<link>http://www.merchantaccountblog.com/735/pa-dss-and-you-thought-pci-was-a-mess</link>
		<comments>http://www.merchantaccountblog.com/735/pa-dss-and-you-thought-pci-was-a-mess#comments</comments>
		<pubDate>Fri, 22 May 2009 16:26:01 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>
		<category><![CDATA[My Favorite Posts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735</guid>
		<description><![CDATA[PA-DSS, is a security standard set for payment application developers, outlining security and auditing procedures for electronic payment applications. Software that falls under the PA-DSS envelope could include anything from a POS system to online shopping cart software. PA-DSS requires that a program be audited by a 3rd party and pass a series of security [...]]]></description>
			<content:encoded><![CDATA[<p><a href="https://www.pcisecuritystandards.org/security_standards/pa_dss.shtml">PA-DSS</a>, is a security standard set for payment application developers, outlining security and auditing procedures for electronic payment applications. Software that falls under the PA-DSS envelope could include anything from a POS system to online shopping cart software. PA-DSS requires that a program be audited by a 3rd party and pass a series of security test and adhere to best-practices before it can be distributed. If it is not audited or fails any part of the audit, it cannot be used as a payment application.</p>
<blockquote cite="Visa"><p><strong>Phase V &#8211; July 1, 2010</strong><br />
Phase V mandates the use of payment applications that support PCI OSS compliance, requiring acquirers, merchants and agents to use only those payment applications that can be validated as PA-DSS compliant.</p></blockquote>
<p><center><strong>If you process credit card online and this doesn&#8217;t scare you, it should!</strong></p>
<p><img src="http://www.merchantaccountblog.com/wp-content/uploads/2009/05/storm.jpg" alt="storm" title="storm" width="500" height="375" class="aligncenter size-full wp-image-750" /><br />
</center></p>
<p>Put this into perspective. There are currently millions of websites using paid and open source software for their online stores. Software like Oscommerce, Zen Cart, Magento, and others have millions of users. <strong><a href="https://www.pcisecuritystandards.org/security_standards/vpa/vpa_approval_list.html?mn=&#038;vn=0&#038;ap=10&#038;rg=0">There are only 2</a></strong>, online store software packages that are PA-DSS compliant. If there is not a mass-movement to get software PA-DSS compliant in the next year, almost every single online store will be out of compliance and subject to fines, or being shut down. This is only a small part of the problem. There&#8217;s still thousands of retail businesses using older payment software and the cost of upgrading would be in the millions, assuming it&#8217;s even possible.</p>
<blockquote><p>As <a href="http://www.storefrontbacktalk.com/uncategorized/pa-dss-is-remarkably-misunderstood/">written by Evan Schuman</a><br />
&#8220;Essentially, this standard could cause merchants of all sizes in all industries to have to switch payment application vendors.&#8221;</p></blockquote>
<p><strong>Where the real mess begins&#8230;</strong></p>
<p><span id="more-735"></span>There are currently <a href="https://www.pcisecuritystandards.org/pdfs/pci_pa-dss_list.pdf">about 40 companies</a> certified to perform PA-DSS validation. The cost to certify a single payment application could be $100,000 or more if the application is extremely complicated. There is an additional &#8220;<strong>mandatory</strong>&#8221; yearly fee of $1250 just to be listed as a <a href="https://www.pcisecuritystandards.org/security_standards/vpa/vpa_approval_list.html">Validated Payment Application</a>. Based on cost, and complexity, there&#8217;s not many shopping cart software providers that can come close to getting PA-DSS certified in the next year. Even then, that still leaves the open source solutions, which the majority of all ecommerce sites are using.</p>
<blockquote><p><a href="http://www.thewhir.com/blog/Rick_Wilson/PA-DSS_and_Ecommerce_Web_Hosting">From Rick Wilson</a><br />
&#8220;What about home grown and open source shopping cart solutions? What happens to them on July 1st, 2010. I asked this question to our auditor and his answer was telling, he said that &#8220;essentially if an application can&#8217;t be PA-DSS certified because it&#8217;s not developed by a single entity for example, then the service provider of that entity will need to become PCI Level 1 certified in order to keep offering that and be in compliance&#8221;.</p></blockquote>
<p>Level 1 certification is nearly as expensive as PA-DSS certification, so don&#8217;t expect any relief from if you&#8217;re using a custom or open source solution. They&#8217;ve truly left no way out this time&#8230;</p>
<p><strong>In conclusion&#8230;</strong></p>
<p>We&#8217;re about to experience a payment industry nightmare potentially having the ability to halt commerce as we know it. If you thought that the $20 per month fee from your processor was bad, you&#8217;ll really hate the $50,000 bill when you go to get level 1 certified. If Visa takes the hard-line stance that merchants not using PA-DSS certified software get shut down, it&#8217;s going to get really ugly. The current focus of the processing industry is on PCI-DSS compliance and a slew of new fees and charges related to it. But, in about a year, we&#8217;re going to see the true fallout of implementing ineffective regulations without foresight into what it actually takes to adopt them, or whether they actually do anything. The only thing we got out of the <a href="http://chuvakin.blogspot.com/2009/04/thoughts-and-notes-from-pci-dss-hearing.html">congressional hearing on PCI</a> is that congress thinks it&#8217;s not enough, and merchants think it&#8217;s way too much.</p>
<p>Houston, we&#8217;re about to have a problem!</p>
<p><strong>Related reading&#8230;</strong><br />
<a href="http://www.treasuryinstitute.org/blog/index.php?itemid=67">PA DSS in One Easy Lesson&#8230;Sort Of</a><br />
<a href="http://www.storefrontbacktalk.com/uncategorized/pa-dss-is-remarkably-misunderstood/">PA DSS Is Remarkably Misunderstood</a><br />
<a href="http://www.thewhir.com/blog/Rick_Wilson/PA-DSS_and_Ecommerce_Web_Hosting">PA-DSS and Ecommerce Web Hosting</a><a href="http://www.merchantaccountblog.com/wp-content/uploads/2009/05/storm.jpg"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/735/pa-dss-and-you-thought-pci-was-a-mess/feed</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Updated Search Engine</title>
		<link>http://www.merchantaccountblog.com/722/updated-search-engine</link>
		<comments>http://www.merchantaccountblog.com/722/updated-search-engine#comments</comments>
		<pubDate>Fri, 03 Apr 2009 16:30:21 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Merchant Accounts]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=722</guid>
		<description><![CDATA[The Merchant Account Search Engine has been updated. It&#8217;s been a while since I&#8217;ve added new sites. I just finished adding about 40 new blogs and informational websites.
As always, please send any recommendations of websites that should be included. Please keep in mind that blogs and websites will only be added if they&#8217;re mostly objective. [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.merchantaccountblog.com/merchant-search">Merchant Account Search Engine</a> has been updated. It&#8217;s been a while since I&#8217;ve added new sites. I just finished adding about 40 new blogs and informational websites.</p>
<p>As always, please send any recommendations of websites that should be included. Please keep in mind that blogs and websites will only be added if they&#8217;re mostly objective. Many of the merchant account blogs out there are only for self-promotional purposes, and these will not be included in the search engine.</p>
<p><span id="more-722"></span></p>
<p><strong>Equipment:</strong><br />
<a href="http://www.magtek.com/">http://www.magtek.com/</a><br />
<a href="http://www.apriva.com/">http://www.apriva.com/</a><br />
<a href="http://www.bluebamboo.com/">http://www.bluebamboo.com/</a><br />
<a href="http://www.waysystems.com">http://www.waysystems.com</a><br />
<a href="http://www.dejavoosystems.com">http://www.dejavoosystems.com</a><br />
<a href="http://www.hypercom.com/">http://www.hypercom.com/</a><br />
<a href="http://www.verifone.com/">http://www.verifone.com/</a><br />
<a href="http://www.ingenico.com/">http://www.ingenico.com/</a><br />
<a href="http://www.magtek.com/">http://www.magtek.com/</a><br />
<a href="http://www.chargeanywhere.com/">http://www.chargeanywhere.com/</a><br />
<a href="http://www.commerciant.com/">http://www.commerciant.com/</a></p>
<p><strong>Blogs:</strong><br />
<a href="http://www.paysimple.com/blog">http://www.paysimple.com/blog</a><br />
<a href="http://paymenttalk.blogspot.com/">http://paymenttalk.blogspot.com/</a><br />
<a href="http://www.glenbrook.com/">http://www.glenbrook.com/</a><br />
<a href="http://blog.bwplawyer.com/">http://blog.bwplawyer.com/</a><br />
<a href="http://googlecheckout.blogspot.com/">http://googlecheckout.blogspot.com/</a><br />
<a href="http://www.paymentsystemsblog.com/">http://www.paymentsystemsblog.com/</a><br />
<a href="http://www.amazonpaymentsblog.com/amazon_payments_blog/">http://www.amazonpaymentsblog.com/amazon_payments_blog/</a><br />
<a href="http://www.andyorrock.com/">http://www.andyorrock.com/</a><br />
<a href="http://blog.elementps.com/element_payment_solutions/">http://blog.elementps.com/element_payment_solutions/</a><br />
<a href="https://www.thepaypalblog.com/">https://www.thepaypalblog.com/</a><br />
<a href="http://waytoohigh.wordpress.com/" rel="nofollow">http://waytoohigh.wordpress.com/</a><br />
<a href="http://pindebit.blogspot.com/">http://pindebit.blogspot.com/</a><br />
<a href="http://aneace.blogspot.com/">http://aneace.blogspot.com/</a><br />
<a href="http://www.storefrontbacktalk.com/">http://www.storefrontbacktalk.com/</a><br />
<a href="http://www.merchant-account-services.org/blog/">http://www.merchant-account-services.org/blog/</a><br />
<a href="http://digitaldebateblogs.typepad.com/digital_money/">http://digitaldebateblogs.typepad.com/digital_money/</a><br />
<a href="http://www.creditcardsonline101.com/">http://www.creditcardsonline101.com/</a></p>
<p><strong>Data Security:</strong><br />
<a href="http://pcidss.wordpress.com/">http://pcidss.wordpress.com/</a><br />
<a href="http://www.pcianswers.com/">http://www.pcianswers.com/</a><br />
<a href="http://www.askaboutpci.com/">http://www.askaboutpci.com/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/722/updated-search-engine/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Credit card interchange vote tomorrow</title>
		<link>http://www.merchantaccountblog.com/710/credit-card-interchange-vote-tomorrow</link>
		<comments>http://www.merchantaccountblog.com/710/credit-card-interchange-vote-tomorrow#comments</comments>
		<pubDate>Tue, 31 Mar 2009 14:11:15 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>
		<category><![CDATA[My Favorite Posts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=710</guid>
		<description><![CDATA[Much to the surprise of the merchant account industry, the congressional bill proposing to regulate interchange, is being attached to the credit reform act and is potentially being voted on tomorrow. Although the interchange regulation bill is related to credit cards and the credit industry, it has nothing to do with the credit reform act, [...]]]></description>
			<content:encoded><![CDATA[<p>Much to the surprise of the merchant account industry, the <a href="http://www.merchantaccountblog.com/341/interchange-regulation-hr-5546">congressional bill proposing to regulate interchange</a>, is being attached to the credit reform act and is potentially being voted on tomorrow. Although the interchange regulation bill is related to credit cards and the credit industry, it has nothing to do with the credit reform act, and is an irresponsible means of passing an already poorly supported bill. The US Government Accountability Office, the US Justice Department, the American Banking Association, and the Federal Trade Commission have all directly warned congress against regulating interchange. To not even have a real vote on the bill is simply irresponsible governing.</p>
<p>Bloggers and advocacy groups like the NRF argue that this bill will level the playing field when it comes to processing costs. This may be true for huge retailers like Walmart, but will almost certainly reduce the quality of processing services to the small business in addition to a much greater overall cost. Just name a situation where government regulation ends in better quality services at a lower cost&#8230;</p>
<p>The argument against interchange has been fought by twisting the reality in what interchange is, who it goes to, why it&#8217;s charged, all by large corporations and angry merchants. While the US has some of the highest interchange costs in the world, we also have the lowest overall processing costs, the lowest setup cost, and by far the highest quality services in the world. In some countries, you would have to pay over a thousand dollars just to get setup processing credit cards, and your monthly bill could easily be double for the exact same services, all with lower interchange. Creating a non-competitive environment like the one proposed by regulating interchange, will create a situation much like the one described above.</p>
<p>I urge anyone in the processing industry, and anyone that stands against huge corporations like Walmart leveraging the government and small business owners to fight a cause that hurts everyone, to <a href="http://capwiz.com/electronicpaymentscoalition/issues/alert/?alertid=13038641">contact their representation</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/710/credit-card-interchange-vote-tomorrow/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Visa Alerts of Floral Credit Card Fraud</title>
		<link>http://www.merchantaccountblog.com/699/visa-alerts-of-floral-credit-card-fraud</link>
		<comments>http://www.merchantaccountblog.com/699/visa-alerts-of-floral-credit-card-fraud#comments</comments>
		<pubDate>Wed, 11 Feb 2009 16:45:40 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=699</guid>
		<description><![CDATA[Visa issued another security alert today specifically for Floral Merchants. Given that Valentines Day is a few days off, this is important for many businesses out there. None of this is ground breaking news, but extra care should be taken by floral merchants when accepting payments over the phone, fax or online. If you aren&#8217;t, [...]]]></description>
			<content:encoded><![CDATA[<p>Visa issued another security alert today specifically for Floral Merchants. Given that Valentines Day is a few days off, this is important for many businesses out there. None of this is ground breaking news, but extra care should be taken by floral merchants when accepting payments over the phone, fax or online. If you aren&#8217;t, take some extra steps to prevent fraud, CVV2 may help in this case which cost nothing extra to process with. Also, be very wary of extremely large orders. </p>
<p>Typically fraudsters look for times when business are most vulnerable, and when business picks up a lot, oversight is often the result.</p>
<blockquote><p>Illegitimate customers are placing orders for flowers using stolen credit card information. The orders are typically placed via fax, e-mail, and/or hearing-impaired relay calls. The perpetrator then requests that the florists wrap the flower arrangements in various amounts of cash and bill the difference to the credit card number(s) provided. These orders have been known to reach $4,000.00. A shipping address for the order is then provided to the merchant.</p>
<p>In some instances, the perpetrators have been known to hire an unsuspecting accomplice to pick up the flowers in person. This accomplice is then instructed to ship the flowers via UPS or the U.S. Postal Service.</p>
<p>When the true cardholder receives the floral charge on their monthly statement, they will initiate a chargeback, as the order was placed without their authorization. As a result, the merchant will become liable for the fraudulent sale.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/699/visa-alerts-of-floral-credit-card-fraud/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Spotting large scale credit card fraud</title>
		<link>http://www.merchantaccountblog.com/667/spotting-large-scale-credit-card-fraud</link>
		<comments>http://www.merchantaccountblog.com/667/spotting-large-scale-credit-card-fraud#comments</comments>
		<pubDate>Wed, 04 Feb 2009 21:10:27 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=667</guid>
		<description><![CDATA[Card issuers have massive computer systems that handle transaction processing. These companies also have some very advanced and large scale fraud detection systems.
Every time a credit card is reported as stolen, a huge amount of past data about that card is put into a big database. This database of pre-fraud activity is used in a [...]]]></description>
			<content:encoded><![CDATA[<p>Card issuers have massive computer systems that handle transaction processing. These companies also have some very advanced and large scale fraud detection systems.</p>
<p>Every time a credit card is reported as stolen, a huge amount of past data about that card is put into a big database. This database of pre-fraud activity is used in a large algorithm to look for similarities, which can signal the origination of stolen or lost credit card numbers. Since Visa and MasterCard have access to billions of transactions worth of information, they can screen for events that may signal that a business is losing card numbers.</p>
<p>If you were to greatly simplify this system and a map from it, it would look something like this:<br />
<center><img src="http://www.merchantaccountblog.com/images/fraud-detection.gif" alt="Fraud Detection" /></center></p>
<p>In this case, the similarity is a single business where all of the stolen credit cards had been used <strong>before </strong>the cards had been involved in fraudulent activity. This could potentially be the sign of an employee skimming card numbers, or a breach in a database. There are always going to be coincidences involving data on a large scale, but because of the scale, it&#8217;s very difficult to end up with false positive fraud once a margin of error is established.</p>
<p><span id="more-667"></span><center><img src="http://www.merchantaccountblog.com/images/fraud-detection-processors.gif" alt="Processor Fraud Detection" /></center></p>
<p>Let&#8217;s assume there isn&#8217;t any conclusive evidence that cards were stolen from a single business. Issuers are also looking at the processor a business is using. If there is a common processor or processing network that many businesses are using, it could be a signal of a data breach on a processor level.</p>
<p><center><img src="http://www.merchantaccountblog.com/images/fraud-detection-everyone.gif" alt="Processor Fraud Detection" /></center></p>
<p>The similarity in this case is the processor that many of the businesses were using. This is basically how the Heartland breach was discovered. Unfortunately, the only companies that can see fraud like this are ones that have access to huge amounts of past card usage. Their computer systems basically load billions of pieces of data about transactions, the businesses that accepted a customer&#8217;s card, and the processors who processed them. When enough lines meet up at a single point, there&#8217;s a chance that something happened there. It really doesn&#8217;t matter where in the process of a transaction the lines all cross, just that they do cross.</p>
<p>Keep in mind that these diagrams are grossly simplified, think a billion times simplified. But, it&#8217;s easy to see that if you have the right data and know what to look for, fraud can be easy to spot.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/667/spotting-large-scale-credit-card-fraud/feed</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Visa issues security alert</title>
		<link>http://www.merchantaccountblog.com/641/visa-issues-security-alert</link>
		<comments>http://www.merchantaccountblog.com/641/visa-issues-security-alert#comments</comments>
		<pubDate>Mon, 02 Feb 2009 19:03:18 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=641</guid>
		<description><![CDATA[A few days ago, Visa issued a security alert (possibly in reaction to the recent Heartland breach) outlining some specific applications and IP addresses to look out for. What is unique about this alert that I&#8217;ve never seen before is that Visa gave a very specific list of malicious applications to search for on a [...]]]></description>
			<content:encoded><![CDATA[<p>A few days ago, Visa issued a security alert (possibly in reaction to the recent Heartland breach) outlining some specific applications and IP addresses to look out for. What is unique about this alert that I&#8217;ve never seen before is that Visa gave a very specific list of malicious applications to search for on a network/computer, and a specific list of IP&#8217;s to block.</p>
<p>This tells me that Visa has explicitly identified threats, where they are originating from, and these locations are static enough that blocking them would actually do some good <em>(IP blocking is a terrible way to prevent/stop malicious behavior)</em>.</p>
<p><a href='http://www.merchantaccountblog.com/wp-content/uploads/2009/01/visa-inc-data-security-alert-january-29-2009.pdf'>Download the security alert &raquo;</a></p>
<p><span id="more-641"></span><br />
<table width="100%" cellspacing="0" cellpadding="5">
<tr>
<td colspan="3"><b>Table 1, Search for these programs:</b></td>
</tr>
<tr>
<td><b>Filename</b> </td>
<td><b>Purpose </b></td>
<td><b>MD5/SHA-1 Hash(s) or Registry Key</b></td>
</tr>
<tr>
<td>appsqlio.exe </td>
<td>Reverse shell tool </td>
<td>387cda6eb91f0b3a054de20c02320338 </td>
</tr>
<tr>
<td>obsqlio.exe </td>
<td>SQL output redirector </td>
<td>f640e53718bc83cb8bb10b1eafb50edf</td>
</tr>
<tr>
<td>blobsqlio.exe </td>
<td>Packed version of gsecdump </td>
<td>959523fc10584da9bfb31a524ff472aa</td>
</tr>
<tr>
<td>sn.exe </td>
<td>Packet sniffer </td>
<td>e07b83abda5b566b3e9a30515a59ecc3</td>
</tr>
<tr>
<td>msdtsc.exe </td>
<td>Packet sniffer </td>
<td>4724103b13e6ce832fbb2c08a419eac6</td>
</tr>
<tr>
<td>svclhost.exe </td>
<td>Network communication tool </td>
<td>da4ab50185c7b246d1d2c8fa7bd7a5ed </td>
</tr>
<tr>
<td>rexesvr.exe </td>
<td>Command line execution </td>
<td>003f6cda98a40529cc87fd1387714fd7</td>
</tr>
<tr>
<td>svcl.exe </td>
<td>Renamed version of sn.exe </td>
<td>e07b83abda5b566b3e9a30515a59ecc3 </td>
</tr>
<tr>
<td>eqslquery.exe </td>
<td>Script that automates the installation of rexesvr.exe </td>
<td>bc354dcf5221aea9fae8a3283c09504d </td>
</tr>
<tr>
<td>rarx.exe </td>
<td>Compression tool </td>
<td>fd729427144044730c572fd5b9be7dd9</td>
</tr>
<tr>
<td>Soft.exe </td>
<td>Backdoor </td>
<td>ea75939da539a3879e5b442b11b51f24 </td>
</tr>
<tr>
<td>lsasstd.exe </td>
<td>Backdoor </td>
<td>07536e77ece9e70f5bf3d6f357c77b04</td>
</tr>
<tr>
<td>lsasstm.exe </td>
<td>Backdoor </td>
<td>e2736b8e0628a07fc3a6dcccad99245e</td>
</tr>
<tr>
<td>smn.exe </td>
<td>Backdoor </td>
<td>b0ff54c190455feda3f67b53c4a4453d</td>
</tr>
<tr>
<td>mstsk.exe </td>
<td>Utility to inject code on running processes </td>
<td>ddfd9073a5f222e223f5f2156c71629d </td>
</tr>
<tr>
<td colspan="3"><a href="/Malicious-Software-Jan-2009.pdf">Download original&#8230;</a></td>
</tr>
</table>
<p><em>Please note that normal windows processes may run under the same filename. Do not assume that a process is suspect unless the MD5 hash matches the one in the table. If you need a MD5 hash generator, <a href="http://www.download.com/DigestIT-2004/3000-2248_4-10387706.html">try this one for free</a>.</em></p>
<table width="100%" cellspacing="0" cellpadding="5">
<tr>
<td colspan="4"><b>Table 2, Block these IP addresses:</b></td>
</tr>
<tr>
<td>90.15.59.86 </td>
<td>85.221.136.196</td>
<td>216.55.164.44 </td>
<td>82.13.14.61 </td>
</tr>
<tr>
<td>85.221.196.131</td>
<td>77.253.115.137</td>
<td>200.115.173.25 </td>
<td>83.99.227.209 </td>
</tr>
<tr>
<td>85.221.138.252</td>
<td>213.84.163.246</td>
<td>85.17.239.11 </td>
<td>89.114.215.182 </td>
</tr>
<tr>
<td>64.247.58.239 </td>
<td>83.110.17.228 </td>
<td>82.13.14.61 </td>
<td>91.177.6.209 </td>
</tr>
<tr>
<td>89.37.241.180 </td>
<td>12.210.14.103 </td>
<td>193.11.110.32 </td>
<td>216.55.126.167 </td>
</tr>
<tr>
<td>83.4.164.214 </td>
<td>74.138.172.183</td>
<td>207.255.204.160</td>
<td>216.55.185.9 </td>
</tr>
<tr>
<td>72.36.215.253 </td>
<td>85.17.239.11 </td>
<td>216.244.34.155 </td>
<td>212.126.1.244 </td>
</tr>
<tr>
<td>202.71.103.77 </td>
<td>69.244.206.15 </td>
<td>24.159.22.70 </td>
<td>212.126.9.154 </td>
</tr>
<tr>
<td>194.146.248.7 </td>
<td>69.141.149.138</td>
<td>67.182.137.29 </td>
<td>212.126.11.27 </td>
</tr>
<tr>
<td>85.17.105.34 </td>
<td>88.156.44.152 </td>
<td>67.85.92.181 </td>
<td>212.126.12.89 </td>
</tr>
<tr>
<td>91.193.63.15 </td>
<td>216.80.124.225</td>
<td>68.50.185.130 </td>
<td>212.126.14.197</td>
</tr>
<tr>
<td>89.37.240.118 </td>
<td>76.100.75.1 </td>
<td>68.94.212.161 </td>
<td>212.126.18.171</td>
</tr>
<tr>
<td>91.145.136.65 </td>
<td>216.196.173.93</td>
<td>69.110.26.21 </td>
<td>212.126.20.83 </td>
</tr>
<tr>
<td>82.232.177.64 </td>
<td>75.64.114.45 </td>
<td>69.14.110.49 </td>
<td>212.126.22.64 </td>
</tr>
<tr>
<td>89.76.218.105 </td>
<td>89.32.130.86 </td>
<td>69.212.211.243 </td>
<td>212.126.25.247</td>
</tr>
<tr>
<td>89.37.241.241 </td>
<td>58.65.239.58 </td>
<td>70.162.2.249 </td>
<td>212.126.31.182</td>
</tr>
<tr>
<td>89.76.220.36 </td>
<td>66.36.229.201 </td>
<td>71.238.147.129 </td>
<td>212.126.32.67 </td>
</tr>
<tr>
<td>83.55.141.204 </td>
<td>74.54.131.130 </td>
<td>71.239.155.202 </td>
<td>212.126.46.199</td>
</tr>
<tr>
<td>216.55.169.234</td>
<td>74.53.114.16 </td>
<td>72.242.241.189 </td>
<td>212.126.47.93 </td>
</tr>
<tr>
<td>89.43.45.232 </td>
<td>203.190.175.39 </td>
<td>74.62.212.143 </td>
<td>212.126.53.23 </td>
</tr>
<tr>
<td>62.21.81.104 </td>
<td>203.190.172.18 </td>
<td>75.118.180.255 </td>
<td>212.126.55.166</td>
</tr>
<tr>
<td>89.37.242.28 </td>
<td>69.70.122.98 </td>
<td>76.204.117.205 </td>
<td>212.126.57.215</td>
</tr>
<tr>
<td>89.43.45.159 </td>
<td>65.111.171.20 </td>
<td>76.22.3.137 </td>
<td>212.126.72.14 </td>
</tr>
<tr>
<td>77.253.108.16 </td>
<td>65.111.171.21 </td>
<td>76.239.29.46 </td>
<td>212.126.73.220</td>
</tr>
<tr>
<td>91.189.139.168</td>
<td>174.36.196.207 </td>
<td>76.242.106.40 </td>
<td>212.126.78.153</td>
</tr>
<tr>
<td>79.9.108.226 </td>
<td>208.43.74.19 </td>
<td>79.118.160.231 </td>
<td>212.126.83.57 </td>
</tr>
<tr>
<td>88.214.208.44 </td>
<td>216.55.162.167 </td>
<td>79.139.245.79 </td>
<td>212.126.84.117</td>
</tr>
<tr>
<td>212.126.94.174</td>
<td>212.126.92.167</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td colspan="3"><a href="/Malicious-IP-Address-Jan-2009.pdf">Download original&#8230;</a></td>
</tr>
</table>
<p><em>The IP&#8217;s above have somehow been identified as being related to malicious behavior, but by just blocking them you are not making your system inherently secure. Blocking IP addresses is generally not an effective or long-term method of preventing malicious access. There are over 2 Billion possible IP addresses, and each IP can have a virtually unlimited number of computers and networks behind it. If you block an IP address, there are a billion others that could be used for malicious behavior. Also, wrongfully blocking an IP address could potentially restrict a huge number of people from your network. In the case of a website, this could result in significant loss of business. Please make sure you understand exactly what you are doing when searching for applications, or blocking IP&#8217;s. If in doubt, contact someone more qualified in network security.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/641/visa-issues-security-alert/feed</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Just how big was the Heartland security breach?</title>
		<link>http://www.merchantaccountblog.com/632/just-how-big-was-the-heartland-security-breach</link>
		<comments>http://www.merchantaccountblog.com/632/just-how-big-was-the-heartland-security-breach#comments</comments>
		<pubDate>Tue, 27 Jan 2009 23:56:59 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=632</guid>
		<description><![CDATA[I have been looking over a 2007 Nilson Report, specifically about the number of credit cards being used in the US. I then though, how much of an impact could the heartland security breach have on the US credit card industry as a whole? How big is the US credit card industry?
To start off, it [...]]]></description>
			<content:encoded><![CDATA[<p>I have been looking over a 2007 <a href="http://www.nilsonreport.com/">Nilson Report</a>, specifically about the number of credit cards being used in the US. I then though, how much of an impact could the heartland security breach have on the US credit card industry as a whole? How big is the US credit card industry?</p>
<p>To start off, it is still unknown how many card numbers were actually stolen in the Heartland Breach. But, it is known that as many as 600 Million card numbers were exposed to malicious software. In terms of security <em>(and logic in general)</em>, you can only assume the worst case until you can later prove that the situation is better <em>(There is no innocent until proven guilty when it comes to security)</em>. So how many cards is 600 Million?</p>
<p>These are not exact numbers but are close&#8230; In 2007, there were about 200 Million card holders in the US. Of these card holders, they owned 321 Million Visa cards, 279 Million MasterCard cards, 52 Million AMEX cards, and 57 Million Discover cards. This makes a total of 709 Million credit cards. Since the account activity averages about 60% across all cards, there are roughly 420 Million active credit cards being used in the US.</p>
<p>Now putting this all together, <strong>the number of cards potentially stolen is about 50% more than every single active card of every cardholder in the entire country</strong>. Given the size of the breach, it&#8217;s unlikely that your card was not compromised if you made a purchase in the US between April and December.</p>
<p>Unfortunately a breach like this will have a negative impact of the entire credit card industry. I&#8217;ve heard a lot of &#8220;they had it coming&#8221; and cheers of joy from other people in my industry, but make no mistake, this is bad for everyone! We have yet to see the real start of what this is going to cost heartland and the credit card industry as a whole. I cannot imagine a scenario where Heartland comes out of this in one piece. They may prove me wrong, but the damage from this looks to be too great for any processor in the world to reasonable handle.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/632/just-how-big-was-the-heartland-security-breach/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Heartland Suffers Massive Data Breach – update</title>
		<link>http://www.merchantaccountblog.com/612/heartland-suffers-massive-data-breach</link>
		<comments>http://www.merchantaccountblog.com/612/heartland-suffers-massive-data-breach#comments</comments>
		<pubDate>Wed, 21 Jan 2009 01:13:32 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=612</guid>
		<description><![CDATA[Heartland payment systems today has been reported to have been victim to one of the largest credit card data breaches in history. 
Heartland discovered malicious software that was recording credit card information as it was being sent to heartland for processing. Heartland processes roughly 100 millions transactions per month, for 250,000 US businesses.
The data stolen [...]]]></description>
			<content:encoded><![CDATA[<p>Heartland payment systems today has been <a href="http://voices.washingtonpost.com/securityfix/2009/01/payment_processor_breach_may_b.html">reported to have been victim to one of the largest credit card data breaches in history</a>. </p>
<p>Heartland discovered malicious software that was recording credit card information as it was being sent to heartland for processing. Heartland processes roughly 100 millions transactions per month, for 250,000 US businesses.</p>
<blockquote><p>The data stolen includes the digital information encoded onto the magnetic stripe built into the backs of credit and debit cards. Armed with this data, thieves can fashion counterfeit credit cards by imprinting the same stolen information onto fabricated cards. </p></blockquote>
<p>Right now it is currently unknown how much data has been collected, how/if it has been used, or how long the malicious software was recording information. The current largest data breach in history was about 45 million card number by TJX (TJ Max and Marshals) which <a href="http://blog.wired.com/27bstroke6/2007/03/data_breach_wil.html">cost the retailer almost $2 Billion dollars</a>. Depending on how much data was lost, this breach could surpass the cost of the TJX breach.</p>
<p>I&#8217;ve been reading comments on various blogs and new sites on the internet and so far there is a lot of backlash and anger from consumers and businesses. We&#8217;ll see in the near future how this breach will affect Heartland, but it seems safe to assume that this will be an extremely costly event for one of America&#8217;s largest ISO&#8217;s.</p>
<p><strong>***UPDATE***</strong></p>
<p><a href="http://www.nytimes.com/2009/01/21/technology/21breach.html?_r=1&#038;emc=tnt&#038;tntemail0=y">http://www.nytimes.com/2009/01/21/technology/21breach.html?_r=1&#038;emc=tnt&#038;tntemail0=y</a></p>
<p>The software on the Heartland&#8217;s network was installed as early as May. Based on the volume of transactions, as many as 600 million card numbers were potentially vulnerable, although the actual number stolen was likely less than this. With that sort of exposure, and the sheer number of merchants that process with heartland, it&#8217;s not impossible that every single card holder in the US was exposed in this data breach.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/612/heartland-suffers-massive-data-breach/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Merchant accounts as a measurement of the economy</title>
		<link>http://www.merchantaccountblog.com/590/merchant-accounts-as-a-measurement-of-the-economy</link>
		<comments>http://www.merchantaccountblog.com/590/merchant-accounts-as-a-measurement-of-the-economy#comments</comments>
		<pubDate>Tue, 13 Jan 2009 21:00:26 +0000</pubDate>
		<dc:creator>jestep</dc:creator>
				<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=590</guid>
		<description><![CDATA[During a recession or a downturn in the country&#8217;s economy, we typically see the unemployment rate go up. In the current situation, the unemployment  rate has gone up a lot.
One of the few good things that comes from unemployment, is that it creates situations that allow new businesses to start up. What better motivation [...]]]></description>
			<content:encoded><![CDATA[<p>During a recession or a downturn in the country&#8217;s economy, we typically see the unemployment rate go up. In the current situation, the unemployment  rate has gone up a lot.</p>
<p>One of the few good things that comes from unemployment, is that it creates situations that allow new businesses to start up. What better motivation to start your own business than getting laid off?</p>
<p>One of the interesting facts about the credit card processing industry, is that we generally see an increase in new businesses during an economic downturn, especially when it involves a lot of lay offs and lost jobs.</p>
<p><center><a href="http://www.google.com/trends/viz?q=merchant+account&#038;date=ytd&#038;geo=usa&#038;graph=weekly_img&#038;sort=0&#038;sa=N"><img src="http://www.google.com/trends/viz?q=merchant+account&#038;date=2008&#038;geo=us&#038;graph=weekly_img&#038;sort=0&#038;sa=N" alt="Economy - Merchant Account Trends" /></a></center></p>
<p>This is blatantly apparent when comparing Google&#8217;s trend graph for the term &#8220;Merchant Account&#8221; to the S&#038;P500 Index. The increase in searches for merchant account is a delayed inverse to the crash in stock price, which in this case is a good indicator of the country&#8217;s economy.</p>
<p><center><img src="http://www.merchantaccountblog.com/images/sandp-2008.gif" alt="" /></center></p>
<p>This is a positive trend to me, because it&#8217;s apparent that people are still getting out there and trying to open their own businesses. Financing is a major hurdle right now, but there are signs that we will see an increase of new businesses in the months to come. Real-estate is cheap, competition is evaporating, and those businesses who can get established in a difficult economy should excel when things do pick up again.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantaccountblog.com/590/merchant-accounts-as-a-measurement-of-the-economy/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
