Malicious NPM packages attributed to North Korean state actors (blog.phylum.io)

submitted 1 year ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

top 3 comments

sorted by: hot top controversial new old

[-] [email protected] 2 points 1 year ago

Whenever I hear about hackers in North Korea I always wonder how they could support a sophisticated info sec agency with advanced capabilities. I guess I just assumed there isn't really a thriving tech community in NK from which to recruit.

I honestly don't know, maybe this attack is as simple as tricking a maintainer into merging a sketchy commit, and not that sophisticated?

Or do they "purchase capability" from supporters like China or Russia?

[-] [email protected] 2 points 1 year ago

They’re often supported by external resources, like China. There isn’t really a community inside of North Korea to draw from like you’d expect in some more established countries.

In this case the attackers are targeting technologists and convincing them to collaborate on a git repository somewhere. That git repo includes dependencies that are hosted on npm, and require a specific order of installation to trigger the malicious behavior.

When the unwitting dev installs thaw deps for the git reo, they receive the malicious payload as well.

[-] [email protected] 1 points 1 year ago

This attack does seem to be on the simpler side technically.

NK recruits their hackers straight from the elite-ish high schools, trains them in computer science, and send them abroad with the objective to earn money through any technical means. How exactly they do it is pretty much up to them.

I can highly recommend the podcast "The Lazarus Heist" if you want to know more about NKs state hacking ventures: http://www.bbc.co.uk/programmes/w13xtvg9

RSS address: https://podcasts.files.bbci.co.uk/w13xtvg9.rss

this post was submitted on 22 Jul 2023

8 points (100.0% liked)

netsec - Network Security

382 readers

1 users here now

This is the netsec Community, a community-curated aggregator of technical information security content. Our mission is to extract signal from the noise - to provide value to security practitioners, students, researchers, and hackers everywhere.

Content Guidelines:

Content should focus on the "How".
Always try to link to the original source.
Titles should provide context.
Ask Questions with a "[Question]" prefix in the Title.
Hiring Posts must go in the [Hiring] (stickied) Threads.
Commercial advertisement is discouraged.

Discussion Guidelines:

Don't create unnecessary conflict.
No trolling allowed, limit the use of jokes and memes.
Don't complain about content being a PDF.
Be nice to each other, everybody started somewhere.

Prohibited Content:

No populist news articles (CNN, BBC, FOX, etc)
No curated lists.
No social media posts (Facebook, Twitter, etc).
No image-only/video-only posts.
No livestreams.
No Tech Support requests.
No paywalled/regwalled content (use archive.is if possible?)
No commercial advertisement.
No crowdfunding posts.
No personally identifiable information.
No doxxing, and no harrassment of any kind.

founded 1 year ago

MODERATORS

[email protected]