Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

8/22/2014
02:49 PM
Sara Peters
Sara Peters
Quick Hits
Connect Directly
Twitter
RSS
E-Mail
50%
50%

JP Morgan Targeted In New Phishing Campaign

Double-whammy 'Smash and Grab' hits targets with two ways to steal credentials.

Corporate email provider Proofpoint discovered a new phishing campaign, this week, aimed at customers of JP Morgan Chase & Co.

The campaign has been dubbed "Smash and Grab" because it combines two methods of obtaining access credentials.

It uses social engineering tactics to try to persuade users to part with their JP Morgan credentials, specifically, by asking them to click to view a secure message from the bank. It also infects the target with Dyre, a banking Trojan that lifts login data for other places too.

The attack appears to have been launched on Tuesday. Proofpoint saw roughly 150,000 of the phishing emails that day.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
AnonymousMan
50%
50%
AnonymousMan,
User Rank: Moderator
8/25/2014 | 8:53:32 AM
Re: Chase encourages phishing
I was just being sarcastic.  Simple misspelling are possible, but I would suggest something like chasesecurityalert.com or similar.  I don't buy your second argument.  The "no hyperlinks in email" only works for sophisticated users.  For the general population, that HTML email train has left the station IMHO.  It might transfer some risk from the bank to the user though, which is all the more reason to take that approach if you are the bank.
JohnRS
50%
50%
JohnRS,
User Rank: Apprentice
8/22/2014 | 5:42:48 PM
Re: Chase encourages phishing
It's possible.  First, phishing mail claiming to be from a company often comes from a "look alike" domain, something like chasse.com for example.  DMARK doesn't stop this sort of mail at all.

Second, a Chase customer will be more likely to click on a link in a phishing message because regular, valid messages from Chase encourage them to do so.  In their "E-mail Security Information" at the bottom of many of the messages which Chase sends to customers they tell them that if they suspect the authenticity of the message, to "click here" (a link inside the suspect message) - the exact OPPOSITE of what they should be advising customers to do.
AnonymousMan
50%
50%
AnonymousMan,
User Rank: Moderator
8/22/2014 | 5:15:51 PM
Re: Chase encourages phishing
http://agari.com/wp-content/uploads/2013/10/130819_Dmarc_JPMorgan.pdf

"JP Morgan Chase evaluated its options and embraced the DMARC (Domain-based Messaging Authentication and Controls) standard to stop phishing attacks, restore its brand and protect its customers."

emphasis added.  You see, JP Morgan can't be phished anymore.  Nothing to see here folks.
JohnRS
50%
50%
JohnRS,
User Rank: Apprentice
8/22/2014 | 3:04:27 PM
Chase encourages phishing
A phishing attack might be more effective against Chase customers than expected since Chase encourages customers to click on links in phishing messages.

I have some accounts with Chase.  Recently I realized that the boilerplate at the bottom of many of their messages includes instructions regarding phishing messages which is the OPPOSITE of what you should do.  Here it is, from a block boldly labelled "E-mail Security Information":

"If you are concerned about the authenticity of this message, please click here or call the phone number on the back of your credit card. If you would like to learn more about e-mail security or want to report a suspicious e-mail, click here".

Yes, Chase is telling you (twice) to click on a link in a suspected phishing message.  Duh!
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...