Record · github.com
https://github.com/subquery/subql/issues/3047
github.com
A page on github.com is cited by 2 distinct blogs to date (corpus.blog, measured 14 October 2026).
A record is what was published and who pointed at it. corpus.blog does not hold this page: read it at the source, or at its Wayback capture.
2blogs citing
| Period | Blogs | Links |
|---|---|---|
| All time | 2 | 2 |
| Last 90 days | 1 | 1 |
| Last 30 days | 1 | 1 |
| Last 7 days | 0 | 0 |
| First cited | 6 Oct 2026 |
|---|---|
| Latest citation | 6 Oct 2026 |
| Words blogs link it with | 2 |
Words blogs link it with
The words blogs link this page with, by how many different blogs use them.
- github issue #3047 in the subquery repository1 blog
- subquery's github report1 blog
Cited by 2 blogs in 2 posts
One row per blog, the most recently citing first. Each shows the blog's newest citing post; open a row for the others.
Blog
Newest citing post
Date
linuxsecurity.com1 post
SubQuery Supply Chain Attack Targeted Cloud and CI Credentials
linked as “SubQuery's GitHub report”
Read at linuxsecurity.com (opens in a new tab)6 Oct 2026
stepsecurity.io1 post
On October 5, 2026, StepSecurity analyzed @subql/common@5.8.3 on npm and identified a hidden payload that collects credentials and supports remote shell access. It starts during installation and when the package is imported. The code targets developer workstations and CI environments, including GitHub Actions runners and accessible cloud services." name="description"/><meta content=
linked as “GitHub issue #3047 in the SubQuery repository”
Read at stepsecurity.io (opens in a new tab)—
Something wrong with this page’s record? Report a problem with github.com/subquery/subql/issues/3047