-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, If you ran eslint (JavaScript codestyle linter) recently (it was only compromised for an hour), your npm token might have been compromised (~/.npmrc). To identify if you were compromised, run: $ locate eslint-scope | grep -i "eslint-scope/package.json" | xargs jq .version And if any of those show "3.7.2" then you have the bad package version installed. Upstream recommends that you 1) reset your npm token and 2) enable 2fa for npm - both can be done from the npm website. You should probably also check to make sure none of your packages were compromised. There are some more details on the bug report[1]. [1] https://github.com/eslint/eslint-scope/issues/39#issuecomment-404533026 - -- Legoktm _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Due to a recent security incident, all user tokens have been invalidated.

It's sad to see how the npm team could have taken steps to mitigate this situation before hand: https://github.com/npm/npm/pull/4016 Important lesson for everyone (including myself). On Thu, Jul 12, 2018 at 11:42 AM C. Scott Ananian <

wrote: > Further eslint-related packages seem to be infected: > https://github.com/eslint/eslint/issues/10600 > > All WM devs with publish access to npm should be using 2FA, which would > mitigate this issue. > > All WM node packages should also be using npm shrinkwrap files; we

> probably audit that. > --scott > > On Thu, Jul 12, 2018 at 11:30 AM, Kunal Mehta &lt;legoktm(a)member.fsf.org&gt; > wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > Hi, > > > > If you ran eslint (JavaScript codestyle linter) recently (it was only > > compromised for an hour), your npm token might have been compromised > > (~/.npmrc). > > > > To identify if you were compromised, run: > > $ locate eslint-scope | grep -i "eslint-scope/package.json" | xargs jq > > .version > > > > And if any of those show "3.7.2" then you have the bad package version > > installed. > > > > Upstream recommends that you 1) reset your npm token and 2) enable 2fa > > for npm - both can be done from the npm website. You should probably > > also check to make sure none of your packages were compromised. > > > > There are some more details on the bug report[1]. > > > > [1] > >

_______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l