Blog DomainTools Research Federal Government

Return to Sender - A Brief Analysis of a US Postal Service Smishing Campaign

In recent weeks there has been a noticeable uptick in campaigns targeting the US Postal Service (USPS) as an institution, even in the usual deluge of phishing and smishing emails and text messages. The volume of these reaching our families and co-workers within a period of weeks piqued our natural curiosity to dig into it and see where it leads. An example of one of these smishing messages is shown in Figure 1.

Figure 1: An example USPS smishing text

At first glance, the choice of language in the text seems suspect. Likely adopted from another phishing script and used over in this campaign, the phrasing shows signs that it was written by someone that either has English as an additional language, or has limited proficiency and likely relied on a translation service to help craft the message. Thankfully they didn’t have the foresight to use a platform like ChatGPT to help craft the content, which could have generated a more convincing lure.

Pivoting on hamsoraei[.]info

Figure 2: Iris Investigate overview image for hamsoraei[.]info

As we start to look into the domain mentioned in the text message, Figure 2 glows in the dark with a risk score of 100, the highest you can get, reflecting both the infrastructure and other previous malicious activity as well as other domains associated with it. In this case, the score is in part tied to the domain’s start of authority record (SOA), a Yahoo email mehdi\.kh021@yahoo[.]com. This unique email address, containing a backslash, is associated with 71 other domains. From here, guided pivots in Iris Investigate can be a helpful way to quickly identify more domains from this initial indicator of compromise (IOC).

pasted-image.jpeg
Figure 3: Iris Investigate image for hamsoraa[.]ir, zoomed in on associated email addresses

By expanding our search, we can see a host of domains registered by an email address using a familiar naming convention, mehdi.k1989@yahoo[.]com, varying only by the 5 characters after the period in the email. This second email address is associated with 63 domains which also share above average risk scores. We also note a variation of the SOA record email that is missing the “\”–this variation adds an additional 30 domains to our running count of 163 domains at this point of our investigation.

By continuing to pivot through IOCs related to this person of interest, we start to get the full picture of domains and hosting infrastructure related to our investigation. Visualization tools, such as Maltego, allow us to better understand the scope and history of activity and quickly see their connections. Figure 4 shows data from this investigation using a Maltego transform on data from the DomainTools Iris platform.

Figure 4: A Maltego visualization showing connections between domains, IP addresses, and email addresses. Note now there are many domains connected to very few email addresses and hosted on only a handful of IP addresses. These tight clusters of domains are indicative of shared control of these domains by a few, or even one actor.

When looking at indicators like email addresses that have been associated with a fairly high degree of recidivism from a domain registration perspective, it is not uncommon for individuals to reuse these addresses for other purposes as well. This ended up being true here. By using publicly available OSINT sources, you can enumerate and connect additional items related to your investigation. In this case, the person of interest used the same email addresses not only to register for different services, but tied the emails together by using them as back up or secondary emails for a number of other accounts. When these additional accounts are included, we uncover an additional 20 domains tied to the same person. 

When individuals don’t expect this data to come to light, they may become lax in what else they tie to these items, including social media and other accounts that are useful in expanding and adding new prospective avenues for inquiry. This too was present in this investigation as highlighted by the Facebook account we found in Figure 5.

Image 2023-08-29 at 1.48 PM.jpeg
Figure 5: A redacted screenshot of a Facebook account associated with one of the email addresses found as part of this investigation

Reviewing this additional social media information, we have reason to believe our person of interest is an Iranian national who lives and works in Tehran, and who may have attended the Islamic Azad University. From our investigation, it is unclear what level of fluency they have in English, but could prospectively be in keeping with our initial observation that the lure text of the smish was likely not written by someone whose native language is English.

Conclusion

Even though phishing and smishing campaigns have become an unfortunate daily fact of life, they remain a significant source of prospective harm for not only individuals, but the companies and organizations whose services they use. The resulting harm both from a loss perspective as well as the emotional toll on individuals, is added to the cost in time, money, and resources that companies face in defending their customers and ensuring that their brand reputation and business operations are not impacted.

In this article, we were able to start with a single domain found in USPS smishing campaign and pivot out to identify nearly 200 domains and several email addresses associated with this threat actor. These pivots eventually lead us to a Facebook account associated with a person of interest for this campaign.

For those organizations and the law enforcement agencies that help combat and prosecute these criminal acts, being able to quickly and thoroughly identify the infrastructure and individuals associated with it, becomes important in minimizing the harm it causes. DomainTools data and services are curated and designed to identify threats, power investigations, and respond effectively to campaigns such as this.  If you want to know more, please contact us.

IOCS

Emails

[email protected]
[email protected]
[email protected]
mehdi\[email protected]

DomainRisk Score
avinpayamak[.]ir100
parnasharifanimation[.]com100
andishkademedia[.]com100
sharifanimation[.]com100
hamsoraei[.]info100
20update[.]ir90
luxgiftlux[.]com82
academy-fh[.]ir81
behsoo-app[.]ir81
asprlus[.]com80
web3ar[.]cam78
devloper[.]ir77
superonline[.]click76
jettaxi[.]click72
superonlineme[.]ir71
coverir[.]ir70
animationpress[.]ir67
sony1.[i]r65
toseeschool[.]com63
sarazaccessories[.]com60
mehriazist[.]com57
instagramme[.]ir57
parname[.]ir54
esetstore[.]shop52
iranianios[.]com51
bazarchemivevatarebar[.]com50
parsiranwasher[.]com50
pnpcgart[.]com50
pooshbam[.]com50
ts-smart-co[.]com50
ts-tarh[.]com50
siboushop[.]ir50
amoomehdi[.]com49
amoomahdi[.]com49
ganjineman[.]com49
upvc-behinesazan[.]com49
giftaks[.]ir48
adakcharmrasa[.]ir47
7thart-m[.]com46
film-pardaz[.]com46
parskaolin[.]info46
besigni[.]ir46
bankesaz[.]com45
ariyaart[.]com41
silverfood[.]ir37
mehriadarman[.]ir36
siboshop[.]ir36
c730[.]ir36
2line[.]ir36
iosia[.]ir35
kakperess[.]ir35
99web[.]ir35
rahnamaapp[.]site35
stakam[.]ir34
clickbekhar[.]ir34
photoiran-co[.]com34
tashstone[.]org34
idsazan[.]ir34
mediageram[.]ir34
avaper[.]ir34
tashstone[.]com33
toloezarineeghtesad[.]ir33
melkbazme[.]ir33
meymehmarket[.]ir33
sajjadnameni[.]com32
tashstone[.]net32
ghasrelebas[.]ir32
parna-sakhteman[.]ir32
attarionlineme[.]ir32
tekinja[.]com32
raadhouseoffilm[.]ir31
salimal666[.]ir30
arsesraeika[.]ir30
saliamal[.]ir29
alamutstore[.]ir29
arsentrans[.]com28
andishkadehmedia[.]com28
modaverse[.]ir28
emdadtrip[.]com28
digitou[.]ir28
azinpelak[.]ir28
khabarejadid[.]ir28
copycopy[.]ir28
alocms[.]ir28
sepiderooz[.]com28
bartarinhoghooghdan[.]ir28
velaati[.]com28
mooyekamand[.]com28
sahamdaraneedalat[.]ir28
piktakk[.]ir28
pakhshmehrbook[.]ir27
nasrbahar[.]com26
addc[.]ir26
40o[.]ir25
oygar[.]ir23
nod-tia[.]com23
arsesraeika[.]com22
telliranshop[.]com22
iranpishroasia[.]ir21
smartiweb[.]ir20
azinpelak[.]com20
tarhopelak[.]com20
tkolbet[.]com20
pakhshefadak[.]ir20
mngg[.]net20
pazinehpress[.]ir20
hesarakidokhtarane[.]ir18
ebiroll[.]ir18
hamsoraa[.]ir17
gardeshgareirani[.]com16
clickbekhar[.]com15
pishroyadaknovin[.]com15
meki[.]me15
denavasher[.]com15
gdoe[.]ir15
avinpersian[.]com13
wordfa24[.]ir11
alocms[.]com11
sarzaminideal[.]ir11
maharelec[.]com11
flowers-cake[.]ir11
cofeios[.]com11
sibou[.]ir10
bargpichak[.]ir10
cafe7[.]ir10
azinorder[.]ir9
danesh-book[.]ir9
matbazaar[.]se8
bimesaad[.]ir8
ropekaa[.]ir8
datisabzar[.]com5
ghabfather[.]ir5
ghabfather[.]com5
khatekhana[.]ir5
khonegi-kala[.]ir5
drackman2027[.]ir5
taradox[.]ir5
smarticoach[.]ir5
tehranfoton[.]ir5
nadcompelex[.]ir5
rihajeans[.]ir5
20web[.]ir5
raeekala[.]ir5
beautiland[.]net4
timekook[.]ir1
zooby[.]ir1
wp30[.]ir1
instasos[.]ir1
itunes24[.]ir1
tarna[.]ir1
appomobil[.]ir1