How Two Malicious NPM Packages Targeted & Sabotaged Others.

An attacker allegedly gained access to an npm user account and published modules that broke dependents. But why?

Jarrod Overson
Jul 22, 2019 · 7 min read
Image for post
Image for post
https://twitter.com/shinnn_tw/status/1149778273024520197

Background

Timeline

Attack details

load-from-cwd-or-npm

purescript-installer
└─┬ dl-tar
└─┬ load-request-from-cwd-or-npm
└── load-from-cwd-or-npm <<<<<<< compromised package

rate-map

So what happened?

Why it matters.

Image for post
Image for post
Image for post
Image for post
rate-map version list with the missing 1.0.3 version

Jarrod Overson

Written by

I write about JavaScript, Reverse Engineering, Security, and Credential Stuffing. Also a speaker, O'Reilly Author, creator of Plato, Director at Shape Security.

Jarrod Overson

Written by

I write about JavaScript, Reverse Engineering, Security, and Credential Stuffing. Also a speaker, O'Reilly Author, creator of Plato, Director at Shape Security.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store