FUfulafel·Jul 13, 2018Submission
RunKit's eslint-scope-scan virus tracking
1 points · Open discussionrunkitdev
eslint-scope-scan
OPEN SOURCE2018–2018
runkitdev / eslint-scope-scan
eslint-scope-scan
runkit.com's scanning results over all packages on npm for the eslint-scope virus
2Distinct people
2Mentions
0Explicit recommenders
27GitHub stars
What to know before exploring
What it is
runkit.com's scanning results over all packages on npm for the eslint-scope virus
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by hour2 dated mentions
Observed mentions: 2018-07-12 23:40:31 UTC to 2018-07-13 06:07:24 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jul 12, 23:00 | 2018-07-12 23:00:00 UTC | 2018-07-13 00:00:00 UTC | 1 | 0 | 1 |
| Jul 13, 00:00 | 2018-07-13 00:00:00 UTC | 2018-07-13 01:00:00 UTC | 0 | 0 | 0 |
| Jul 13, 01:00 | 2018-07-13 01:00:00 UTC | 2018-07-13 02:00:00 UTC | 0 | 0 | 0 |
| Jul 13, 02:00 | 2018-07-13 02:00:00 UTC | 2018-07-13 03:00:00 UTC | 0 | 0 | 0 |
| Jul 13, 03:00 | 2018-07-13 03:00:00 UTC | 2018-07-13 04:00:00 UTC | 0 | 0 | 0 |
| Jul 13, 04:00 | 2018-07-13 04:00:00 UTC | 2018-07-13 05:00:00 UTC | 0 | 0 | 0 |
| Jul 13, 05:00 | 2018-07-13 05:00:00 UTC | 2018-07-13 06:00:00 UTC | 0 | 0 | 0 |
| Jul 13, 06:00 | 2018-07-13 06:00:00 UTC | 2018-07-13 07:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesWhen we heard about this this morning at RunKit we immediately started writing a script to identify if any other packages had been possibly affected. We're in a pretty unique position since we install every version of every package in a sandbox environment as soon as it is published. The scan is pretty simple (just looking for a few key strings), and designed to catch any pre-discovery propagation. The scan is running as we speak and we've unfortunately found at least one unreported case. Luckily it seems to be a package not in too frequent use, and the way the virus propagated was also pretty bizarre (through `bundledDependencies`).
We've created a GitHub repo to track our progress that you can visit here: https://github.com/runkitdev/eslint-scope-scan
We will immediately file issues on any packages we find the exploit in. We are also op
Read the rest
en to suggestions to more sophisticated further approaches after this initial scan. Additionally, we are internally working on adding some sanity checks to the installation pipeline that might one day catch this sooner (such as monitoring network requests and file modifications during our sandbox install). Please let us know if you have any other ideas.