United States v. Hasston, Inc.

75 F. Supp. 3d 101, 2014 WL 6735479, 2014 U.S. Dist. LEXIS 166156
CourtDistrict Court, District of Columbia
DecidedDecember 1, 2014
DocketCriminal No. 2013-0274
StatusPublished
Cited by8 cases

This text of 75 F. Supp. 3d 101 (United States v. Hasston, Inc.) is published on Counsel Stack Legal Research, covering District Court, District of Columbia primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
United States v. Hasston, Inc., 75 F. Supp. 3d 101, 2014 WL 6735479, 2014 U.S. Dist. LEXIS 166156 (D.D.C. 2014).

Opinion

MEMORANDUM OPINION

Re Document No.: 28

RUDOLPH CONTRERAS, United States District Judge

Denying Defendant’s Motion to Suppress

I. INTRODUCTION

Defendant Shantia Hassanshahi is charged with one count of conspiracy to violate the International Economic Emergency Powers Act, 50 U.S.C. § 1705, and the Iranian Transactions and Sanctions Regulations, 31 C.F.R. §§ 560.203-204, commonly referred to as the United States’ trade embargo against Iran. Now before the Court is Hassanshahi’s motion to suppress evidence uncovered during a forensic examination of his laptop following an international border stop at Los Ange-les International Airport on the basis that the laptop examination violated the Fourth Amendment. Upon consideration of Has-sanshahi’s motion and the opposition thereto, the Court reaches two conclusions: first, the exclusionary rule does not require suppressing the laptop evidence as fruit of the poisonous tree because discovery of that evidence was sufficiently attenuated from the initial unlawful telephone database search; and second, reasonable suspicion existed for conducting the forensic examination after Hassanshahi landed at the airport. Accordingly, the Court will deny Hassanshahi’s motion to suppress.

*105 II. FACTUAL BACKGROUND 1

On August 16, 2011, Homeland Security Investigations (“HSI”) received an unsolicited e-mail from a source indicating that the source had received an e-mail from an Iranian known as M. Sheikhi who, on behalf of his Iranian company, sought the source’s assistance in procuring protection relays for an Iranian power' project. See Akronowitz Aff., ECF No. 37-1 (“2d Akro-nowitz Aff.”) at ¶ 2. The e-mail from Shei-khi to the source contained an Iranian business telephone number and the address for Sheikhi’s company in Tehran, Iran. See id. An HSI agent used the telephone number associated with Sheikhi to search an “HSI-aceessible law enforcement database” in the hope of identifying potential U.S.-based targets engaged in the sale or export of protection relays for use in Iran. See id. ¶ 3. The HSI agent’s search returned a single telephone record indicating one call between Sheikhi’s telephone number and a telephone number with an “818” area code (the “818 number”), which is the area code for Los Ange-les, California. See id. ¶ 4.

After discovering that the 818 number was assigned to Google/Google Voice, see id. ¶ 13, HSI prepared and served on Google an Administrative Export Enforcement Control Subpoena (“AEEC Subpoena”). See id. ¶ 14. In response, Google provided information that identified Hassanshahi as the person to whom the 818 number was registered, and Google also provided an email address registered to Hassanshahi. See id. ¶ 15. In addition, Google provided call log information for the period between September 6, 2011, and October 6, 2011, which showed that the 818 number had received one telephone call from an unknown Iranian phone number on October 5,2011. See id.-, Revised Akronowitz Aff., ECF No. 42-1 (“3d Akronowitz Aff.”) at ¶ 15. The Google call log information also revealed one missed call between Has-sanshahi’s 818 number and an unknown Iranian cell phone number on September 19, 2011. See 2d Akronowitz Aff. ¶ 15.

On October 18, 2011, the HSI agent searched the Department of Homeland Security’s (“DHS”) TECS database for additional information about Hassanshahi. 2 See id. ¶ 16. TECS led the agent to discover that Hassanshahi was involved in a prior federal law enforcement investigation into potential violations of the Iran trade embargo. 3 See id. ¶ 16a. Specifically, the *106 investigation occurred in 2003 through an HSI office in California, and the investigation uncovered that Hassanshahi and two partners had established an American company for the purpose of entering into an agreement with a Chinese company to build a computer production facility in Iran. See id. Hassanshahi’s American company later filed a breach-of-contract claim against the Chinese company in California state court, and that lawsuit was dismissed in part because the contract was unenforceable as against public policy since it involved doing business in Iran, a clear violation of U.S. law. See id. The Department of Justice did not file criminal charges against Hassanshahi for his role in this venture. See id.

The TECS search also revealed a number of earlier instances in which Hassansh-ahi reentered the U.S. after traveling to the Middle East, including: an incident in 2005 when Hassanshahi was questioned by U.S. Customs and Border Protection (“CBP”) agents after returning from Dubai with $15,000 in cash; an incident in 2006 when Hassanshahi returned from Tehran with a travel companion; and four other returns from Tehran — two in 2008, one in 2010, and one in May 2011. See id. ¶¶ 16c-e. In addition, HSI learned through TECS that Hassanshahi presently was outside the U.S., so HSI supplemented the existing TECS information by entering instructions that HSI should be alerted and Hassanshahi should be referred for secondary screening the next time he returned to the U.S. See id. ¶ 17.

Around December 20, 2011, HSI served Google with a second AEEC Subpoena, this time seeking subscriber information and recent Internet protocol (“IP”) logs for Hassanshahi’s Google e-mail account. See id. ¶ 18. In response, Google provided information indicating that Hassanshahi’s e-mail account was accessed from an Iran IP address twenty-four times between December 8, 2011, and December 15, 2011. See id. The information provided by Google also showed, however, that Hassansh-ahi’s e-mail account was accessed from a U.S. IP address on the same day it apparently was accessed from an Iran IP address, including sometimes within just a few minutes of each other. See Def.’s Reply Supp. Mot. Dismiss Ex. 1 at 27 (Google Subscriber Information). And on another occasion, Hassanshahi’s e-mail account apparently was accessed on the same day from an Iran IP address, a Germany IP address, and a U.S. IP address, occasionally alternating between the countries within minutes. See id. at 30.

On January 11, 2012, HSI was alerted that Hassanshahi would be returning to the U.S. the next day through Los Angeles International Airport (“LAX”). See 2d Akronowitz Aff. ¶ 19. When Hassanshahi *107

Free access — add to your briefcase to read the full text and ask questions with AI

Related

United States v. Brewer
District of Columbia, 2025
United States v. Mitchell
District of Columbia, 2024
United States v. Miguel Cano
973 F.3d 966 (Ninth Circuit, 2020)
United States v. Manafort
District of Columbia, 2018
United States v. Manafort
313 F. Supp. 3d 213 (D.C. Circuit, 2018)
United States v. Hasston, Inc.
145 F. Supp. 3d 75 (District of Columbia, 2015)
United States v. Jae Shik Kim
103 F. Supp. 3d 32 (District of Columbia, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
75 F. Supp. 3d 101, 2014 WL 6735479, 2014 U.S. Dist. LEXIS 166156, Counsel Stack Legal Research, https://law.counselstack.com/opinion/united-states-v-hasston-inc-dcd-2014.