Skip to content

Instantly share code, notes, and snippets.

class Cell {
constructor(alive) {
this.alive = alive;
}
toggle() {
this.alive = !this.alive;
}
copy() {
@sarahmeyer
sarahmeyer / npm_eslint-scope_explainer.md
Last active July 14, 2018 16:50
explainer of the july 12 2018 npm/eslint vulnerability

What happened to npm yesterday?

This morning, soon after I got to work, one of my favorite coworkers sent me a direct message on Slack. They had heard a lot of discussion yesterday in our internal #front-end-devs channel about a malicious script making its way into an npm package called eslint-scope. After following the chat and reading the issue report on Github, they could tell that the attack exposed a vulnerability in the npm package ecosystem, and that the purpose of it was to harvest the contents of .npmrc files. They had a simple question:

why would someone steal npm credentials? what are they good for?

This coworker of mine is very smart, and if they didn't know the answer to this question, I thought it might be possible that other folks didn't know it, either.

What did the attacker try to steal?

<!DOCTYPE html>
<html>
<head>
<title>TITLE OF YOUR WEBPAGE</title>
<link href="index.css" rel="stylesheet">
</head>
<body>
<img src="URL OF AN IMAGE" />
<h1>TITLE OF YOUR WEBPAGE</h1>
<p>TELL ME SOMETHING</p>