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.

ABTV //

Phishing

2/6/2018
08:05 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

North Korea Stole 'Billions' in Cryptocurrency Heist, Official Claims

A South Korean official claims that North Korea used a phishing scheme to steal 'billions' in cryptocurrency, according to a published report.

A member of the South Korean parliament charges that North Korea used a phishing scheme in a massive cryptocurrency theft, according to several published reports.

Kim Byung-kee, a member of South Korea's parliamentary intelligence committee, made the charges on Monday (February 5), and claimed that only did the North Koreans steal cryptocurrency in 2017, but the country is continuing to penetrate South Korean exchanges this year.

In terms of how much was taken, Kim only noted it was in the billions of won -- the country's official currency. One estimate reckons a billion won in cryptocurrency could be worth about $920,000.

"North Korea sent emails that could hack into cryptocurrency exchanges and their customers' private information and stole (cryptocurrency) worth billions of won," said Kim, according to the Reuters report.

The report noted that South Korea's intelligence agency has been trying to stop the current attacks on the country's exchanges.

While details about the scheme were scarce, the Korea Herald reported that North Korean hackers used a series of emails or social media messages to steal customers' passwords and other personal information. North Korea also appears to have used technology from a South Korean company to thwart anti-hacking tools.

By shrouding itself in secrecy, North Korea has made it difficult for others to gauge its hacking and cyber warfare capabilities. Periodic reports from South Korea intelligence offer some information, but it's hard to verify what one country claims about the other.


The fundamentals of network security are being redefined – don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth annual Big Communications Event. There's still time to register and communications service providers get in free!

However, it's believed by security and intelligence experts that North Korea, officially the Democratic People's Republic of Korea or DPRK, has an extensive cyber warfare operation that has committed a series of financial crimes. (See Cybercrime Is North Korea's Biggest Threat.)

Specifically DPRK Office 91, which is also known as the Lazarus Group, is suspected of being behind the WannaCry ransomware attack that was considered one of the largest attacks of 2017. (See Kaspersky Names WannaCry 'Vulnerability of the Year'.)

Earlier this year, McAfee detected a campaign that targeted North Korean dissidents and journalists, and although the report found a North Korean IP address, it's not clear if the group is associated with the country or operating on its own. (See McAfee: Attackers Targeting North Korean Dissidents, Journalists.)

Related posts:

— Scott Ferguson, Editor, Enterprise Cloud News. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Data Breaches Affect the Enterprise
Data breaches continue to cause negative outcomes for companies worldwide. However, many organizations report that major impacts have declined significantly compared with a year ago, suggesting that many have gotten better at containing breach fallout. Download Dark Reading's Report "How Data Breaches Affect the Enterprise" to delve more into this timely topic.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3769
PUBLISHED: 2021-11-30
# Vulnerability in `pygmalion`, `pygmalion-virtualenv` and `refined` themes **Description**: these themes use `print -P` on user-supplied strings to print them to the terminal. All of them do that on git information, particularly the branch name, so if the branch has a specially-crafted name the vul...
CVE-2021-3725
PUBLISHED: 2021-11-30
Vulnerability in dirhistory plugin Description: the widgets that go back and forward in the directory history, triggered by pressing Alt-Left and Alt-Right, use functions that unsafely execute eval on directory names. If you cd into a directory with a carefully-crafted name, then press Alt-Left, the...
CVE-2021-3726
PUBLISHED: 2021-11-30
# Vulnerability in `title` function **Description**: the `title` function defined in `lib/termsupport.zsh` uses `print` to set the terminal title to a user-supplied string. In Oh My Zsh, this function is always used securely, but custom user code could use the `title` function in a way that is unsaf...
CVE-2021-3727
PUBLISHED: 2021-11-30
# Vulnerability in `rand-quote` and `hitokoto` plugins **Description**: the `rand-quote` and `hitokoto` fetch quotes from quotationspage.com and hitokoto.cn respectively, do some process on them and then use `print -P` to print them. If these quotes contained the proper symbols, they could trigger c...
CVE-2021-43790
PUBLISHED: 2021-11-30
Lucet is a native WebAssembly compiler and runtime. There is a bug in the main branch of `lucet-runtime` affecting all versions published to crates.io that allows a use-after-free in an Instance object that could result in memory corruption, data race, or other related issues. This bug was introduce...