Corroboration Monitor · No. 1

Half of Stories Had a Second Organization in Three Days; One in Five Had None

The first Corroboration Monitor follows each activity from its first public report to the day an independent organization reported it too. It counts stories, Asterism's clusters of reports, so a report nobody else wrote about is outside the curve, and in this window that was most of them.

Marking
TLP:CLEAR
Type
Research
Author
Null Sec team
Published
· 5 min read
Applies to
First reports from 19 Sep to 31 Oct 2026
Data
Counts of public reporting in Asterism's panel, as of 13 Nov 2026
An engraving of two lighthouses on rocky headlands across a calm bay, the second one small and far off.

Half of the stories first reported between 19 Sep and 31 Oct 2026 had a second, independent organization reporting them within 2 to 3 days. The count covers 92 stories from 134 organizations. By 13 Nov, 20% of the stories (95% CI 13% to 29%) still had only one.

Key Findings

  • The median wait for a second organization was 2 days (95% CI 1 to 5). Reasonable changes to the sample keep it within 2 to 3 days.
  • On the day of the first report, 26% of the stories already had a second organization, and 54% had one within three days.
  • By the as-of date, at least 14 days after their first report, 20% (95% CI 13% to 29%) had no second organization.
  • Stories that a vendor reported first were corroborated more often (87%, n = 61) than those that began on a community list (63%, n = 19), though the intervals overlap.
  • Stories are the minority: 82% of the window's 2,908 reports joined no story at all.

Days to a Second Organization

Corroboration · first reports 19 Sep to 31 Oct 2026
  • second organization
  • third organization
  • shaded band, the interval
  • tick, still waiting at the as-of date
  • median
Share of stories still waitingDays since the first report0%25%50%75%100%01020304050second organizationthird organizationsecond organization: 1 censored at 14second organization: 1 censored at 15second organization: 1 censored at 16second organization: 1 censored at 22second organization: 1 censored at 28second organization: 2 censored at 29second organization: 1 censored at 31second organization: 1 censored at 33second organization: 1 censored at 38second organization: 1 censored at 42second organization: 1 censored at 44second organization: 3 censored at 45second organization: 1 censored at 47second organization: 1 censored at 49second organization: 1 censored at 53third organization: 2 censored at 14third organization: 2 censored at 15third organization: 3 censored at 16third organization: 1 censored at 17third organization: 1 censored at 19third organization: 2 censored at 20third organization: 1 censored at 21third organization: 4 censored at 22third organization: 1 censored at 23third organization: 5 censored at 24third organization: 2 censored at 25third organization: 1 censored at 26third organization: 1 censored at 28third organization: 5 censored at 29third organization: 2 censored at 30third organization: 2 censored at 31third organization: 2 censored at 32third organization: 1 censored at 33third organization: 1 censored at 36third organization: 1 censored at 37third organization: 1 censored at 38third organization: 1 censored at 39third organization: 1 censored at 41third organization: 3 censored at 42third organization: 1 censored at 43third organization: 2 censored at 44third organization: 3 censored at 45third organization: 1 censored at 47third organization: 3 censored at 49third organization: 1 censored at 50third organization: 2 censored at 52third organization: 4 censored at 53second organization: median 2median 2second organizationthird organizationShare of stories still waitingDays since the first report0%25%50%75%100%02040second organizationthird organizationsecond organization: 1 censored at 14second organization: 1 censored at 15second organization: 1 censored at 16second organization: 1 censored at 22second organization: 1 censored at 28second organization: 2 censored at 29second organization: 1 censored at 31second organization: 1 censored at 33second organization: 1 censored at 38second organization: 1 censored at 42second organization: 1 censored at 44second organization: 3 censored at 45second organization: 1 censored at 47second organization: 1 censored at 49second organization: 1 censored at 53third organization: 2 censored at 14third organization: 2 censored at 15third organization: 3 censored at 16third organization: 1 censored at 17third organization: 1 censored at 19third organization: 2 censored at 20third organization: 1 censored at 21third organization: 4 censored at 22third organization: 1 censored at 23third organization: 5 censored at 24third organization: 2 censored at 25third organization: 1 censored at 26third organization: 1 censored at 28third organization: 5 censored at 29third organization: 2 censored at 30third organization: 2 censored at 31third organization: 2 censored at 32third organization: 1 censored at 33third organization: 1 censored at 36third organization: 1 censored at 37third organization: 1 censored at 38third organization: 1 censored at 39third organization: 1 censored at 41third organization: 3 censored at 42third organization: 1 censored at 43third organization: 2 censored at 44third organization: 3 censored at 45third organization: 1 censored at 47third organization: 3 censored at 49third organization: 1 censored at 50third organization: 2 censored at 52third organization: 4 censored at 53second organization: median 2median 2

as of 13 Nov 2026Measures reporting, not activity.Download CSV

Data table survival.csv
The data behind Fig. 1, from survival.csv.
groupdaysslohicensored
second organization00.7390.6370.8170
second organization10.5540.4470.6490
second organization20.5000.3940.5970
second organization30.4570.3530.5540
second organization40.4020.3020.5000
second organization50.3590.2620.4560
second organization60.2830.1950.3770
second organization70.2720.1860.3650
second organization80.2390.1580.3300
second organization90.2070.1310.2940
second organization100.1960.1220.2820
second organization140.1960.1220.2821
second organization150.1960.1220.2821
second organization160.1960.1220.2821
second organization220.1960.1220.2821
second organization280.1960.1220.2821
second organization290.1960.1220.2822
second organization310.1960.1220.2821
second organization330.1960.1220.2821
second organization380.1960.1220.2821
second organization420.1960.1220.2821
second organization440.1960.1220.2821
second organization450.1960.1220.2823
second organization470.1960.1220.2821
second organization490.1960.1220.2821
second organization530.1960.1220.2821
third organization00.8800.7950.9320
third organization10.7500.6480.8260
third organization20.7390.6370.8170
third organization30.7280.6250.8070
third organization40.7170.6130.7980
third organization50.7070.6020.7880
third organization60.6960.5910.7790
third organization80.6850.5790.7690
third organization140.6850.5790.7692
third organization150.6850.5790.7692
third organization160.6850.5790.7693
third organization170.6850.5790.7691
third organization190.6850.5790.7691
third organization200.6850.5790.7692
third organization210.6850.5790.7691
third organization220.6850.5790.7694
third organization230.6850.5790.7691
third organization240.6850.5790.7695
third organization250.6850.5790.7692
third organization260.6850.5790.7691
third organization280.6850.5790.7691
third organization290.6850.5790.7695
third organization300.6850.5790.7692
third organization310.6850.5790.7692
third organization320.6850.5790.7692
third organization330.6850.5790.7691
third organization360.6850.5790.7691
third organization370.6850.5790.7691
third organization380.6850.5790.7691
third organization390.6850.5790.7691
third organization410.6850.5790.7691
third organization420.6850.5790.7693
third organization430.6850.5790.7691
third organization440.6850.5790.7692
third organization450.6850.5790.7693
third organization470.6850.5790.7691
third organization490.6850.5790.7693
third organization500.6850.5790.7691
third organization520.6850.5790.7692
third organization530.6850.5790.7694
Fig. 1Share of stories still reported by a single organization, by days since the first report, for a second and a third organization. Ticks mark stories still waiting on 13 Nov.Plate I

The teal curve falls fast: on day zero, the day of the first report, 26% of the stories already had a second organization, and by day seven only 27% were still waiting. After two weeks it flattens at 20%: a story that hadn't been picked up by then mostly wasn't picked up at all.

A third organization is rarer: only 29 of the 92 stories reached one, and that curve never falls to one half, so there's no median to give.

On 13 Nov, 18 stories were still waiting. The curve counts each of them up to that day and no further, which is why we use a survival curve: dropping them would make the waits look shorter than they were.

Corroboration by Who Reported First

Corroborated by 13 Nov · by first publisher's category
  • whisker, the interval
Share with a second organization0%20%40%60%80%100%vendorvendor: 87% (76% to 93%), n = 6187%n = 61government or CERTgovernment or CERT: 75% (47% to 91%), n = 1275%n = 12communitycommunity: 63% (41% to 81%), n = 1963%n = 19Share with a secondorganization0%50%100%vendorvendor: 87% (76% to 93%), n = 6187%n = 61government or CERTgovernment or CERT: 75% (47% to 91%), n = 1275%n = 12communitycommunity: 63% (41% to 81%), n = 1963%n = 19

as of 13 Nov 2026Measures reporting, not activity.Download CSV

Data table shares.csv
The data behind Fig. 2, from shares.csv.
categorysharelohin
vendor0.8690.7620.93261
community0.6320.4100.80919
government or CERT0.7500.4680.91112
Fig. 2Share of each group's stories that a second organization reported by 13 Nov, by the category of the first report's publisher, with each share's 95% CI.Plate II

Asterism records a category for each source, and these are the categories of the first publisher. Vendor-first stories were corroborated 87% of the time (95% CI 76% to 93%), government and CERT-first stories 75% (47% to 91%), and community-first stories 63% (41% to 81%). Two of the three groups are small samples, and all three intervals overlap, so read this as a lean, not a ranking.

The community group is mostly one place: the oss-security mailing list, where open-source maintainers and researchers post vulnerability disclosures, was first in 17 of its 19 stories. Not every open-source flaw gets a vendor write-up, which may explain the lower share.

Each Story's Wait

Days to a second organization · one dot a story
  • median
Days to a second organization0246810communitycommunity: median 1community: 0community: 0community: 0community: 1community: 1community: 1community: 1community: 2community: 6community: 6community: 9community: 10government or CERTgovernment or CERT: median 1government or CERT: 0government or CERT: 0government or CERT: 0government or CERT: 0government or CERT: 1government or CERT: 1government or CERT: 1government or CERT: 1government or CERT: 4vendorvendor: median 2vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 2vendor: 2vendor: 2vendor: 2vendor: 3vendor: 3vendor: 3vendor: 3vendor: 4vendor: 4vendor: 4vendor: 4vendor: 5vendor: 5vendor: 5vendor: 5vendor: 6vendor: 6vendor: 6vendor: 6vendor: 6vendor: 7vendor: 8vendor: 8vendor: 8vendor: 9vendor: 9Days to a second organization0246810communitycommunity: median 1community: 0community: 0community: 0community: 1community: 1community: 1community: 1community: 2community: 6community: 6community: 9community: 10government or CERTgovernment or CERT: median 1government or CERT: 0government or CERT: 0government or CERT: 0government or CERT: 0government or CERT: 1government or CERT: 1government or CERT: 1government or CERT: 1government or CERT: 4vendorvendor: median 2vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 0vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 1vendor: 2vendor: 2vendor: 2vendor: 2vendor: 3vendor: 3vendor: 3vendor: 3vendor: 4vendor: 4vendor: 4vendor: 4vendor: 5vendor: 5vendor: 5vendor: 5vendor: 6vendor: 6vendor: 6vendor: 6vendor: 6vendor: 7vendor: 8vendor: 8vendor: 8vendor: 9vendor: 9

as of 13 Nov 2026Measures reporting, not activity.Download CSV

Data table lags.csv
The data behind Fig. 3, from lags.csv.
categorydaysstory
community0
community0
community0
community1
community1
community1
community1
community2
community6
community6
community9
community10
government or CERT0
government or CERT0
government or CERT0
government or CERT0
government or CERT1
government or CERT1
government or CERT1
government or CERT1
government or CERT4
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor0
vendor1
vendor1
vendor1
vendor1
vendor1
vendor1
vendor1
vendor1
vendor1
vendor2
vendor2
vendor2
vendor2
vendor3
vendor3
vendor3
vendor3
vendor4
vendor4
vendor4
vendor4
vendor5
vendor5
vendor5
vendor5
vendor6
vendor6
vendor6
vendor6
vendor6
vendor7
vendor8
vendor8
vendor8
vendor9
vendor9
Fig. 3Days from each corroborated story's first report to its second organization, one dot a story, by the category of the first publisher.Plate III

Most dots sit between zero and three days, and 7 stories waited more than a week for their second organization, the longest 10 days.

Most Reports Stand Alone

Reports a week · 21 Sep to 31 Oct 2026
  • in a story
  • standing alone
Reports a weekWeek starting020040060080021 Sep, in a story: 5521 Sep, standing alone: 32228 Sep, in a story: 5928 Sep, standing alone: 3875 Oct, in a story: 485 Oct, standing alone: 37012 Oct, in a story: 8412 Oct, standing alone: 42719 Oct, in a story: 18319 Oct, standing alone: 48326 Oct, in a story: 9426 Oct, standing alone: 38626 Oct21 Sep28 Sep5 Oct12 Oct19 Oct666480Reports a weekWeek starting020040060080021 Sep, in a story: 5521 Sep, standing alone: 32228 Sep, in a story: 5928 Sep, standing alone: 3875 Oct, in a story: 485 Oct, standing alone: 37012 Oct, in a story: 8412 Oct, standing alone: 42719 Oct, in a story: 18319 Oct, standing alone: 48326 Oct, in a story: 9426 Oct, standing alone: 38626 Oct21 Sep5 Oct666

as of 13 Nov 2026Measures reporting, not activity.Download CSV

Data table weekly.csv
The data behind Fig. 4, from weekly.csv.
weekkindreports
2026-09-21in a story55
2026-09-21standing alone322
2026-09-28in a story59
2026-09-28standing alone387
2026-10-05in a story48
2026-10-05standing alone370
2026-10-12in a story84
2026-10-12standing alone427
2026-10-19in a story183
2026-10-19standing alone483
2026-10-26in a story94
2026-10-26standing alone386
Fig. 4The window's reports each week, split into those that joined a story and those that stood alone. The last week has six days.Plate IV

A story needs two reports about the same activity. Of the window's 2,908 dated intelligence reports, 524 joined a story and 82% (95% CI 81% to 83%) did not. Some of those are one-off research nobody needed to repeat; some are activities a second organization covered under different enough details that the clustering missed the pair. They are outside the curves above, so the curves describe activities that drew at least two reports, not everything published.

The jump in the week of 19 Oct is PHP2Shell, the pair of PHP flaws disclosed on 21 Oct. Within a fortnight, 89 organizations had reported it, in one story.

Limits of This Report

  • This measures reporting, not activity. A fast second report means a second organization published, not that it saw the activity itself. Corroboration is not confirmation: a second organization can repeat the first one's mistake.
  • Independent means a different organization, not independent evidence. In our validation sample, 3 of the 18 second reports added nothing of their own: an article cross-posted on two blogs, a joint advisory published by both of its authors, and a vendor's summary of a government alert. Two of those pairs may be one publisher under two names; counting each as one gives a median of 3 days, and 23% of stories with no second organization.
  • "First report" is the first in Asterism's panel, from publishers that allow AI use. Someone outside the panel may have reported it earlier.
  • Dates are whole days, so a same-day second report is a tie, not a race anyone won.
  • Recent stories had less time. A first report from late October that gets its second report in mid-November isn't a story yet, so it is missing rather than censored. Limiting the sample to first reports up to 15 Oct, which had at least 29 days, gives a median of 3 days (n = 56).
  • The clustering makes mistakes. We corrected one (see the method) and left one: PHP2Shell is split across two stories. Folding the second into the first gives a median of 3 days.
  • The panel grew from 183 sources reporting in the window's first two weeks to 196 in its last two, so later stories had a few more potential witnesses.
  • No source in the window carries Asterism's news category, so this edition can't separate press coverage from original research.
  • We don't rank named publishers by speed, and the data files don't either: they list who reported what, and when.

Method

The definitions of a report, a story, an organization, a first report and corroboration are those of How Null Sec Counts. The population is every story whose first report is dated 19 Sep to 31 Oct 2026 (UTC), as Asterism's stories stood on 13 Nov. The window starts on 19 Sep, the first whole day after Asterism's coverage date. For each story we took each source's earliest report in it, mapped the source to its organization, and measured the days from the first report to the second and third organizations' first reports.

Asterism's MCP server names the organization only for a story's first source, so we mapped the other sources by name, in organizations.csv. Our count of organizations matched Asterism's for every story but two. In one, we count two JPCERT/CC feeds as one publisher where Asterism counts two; Asterism's count gives the same median of 2 days. In the other, PHP2Shell, we left out Arete's "September Threat Trends" page.1 It is dated 15 Oct, a week before the disclosure, but it is a podcast page that later gained articles about events of 21 Oct, so its date isn't when it reported PHP2Shell. With Asterism's dates as they stand, the median is 3 days. The next report in that story, Blackpoint Cyber's, opened on 20 Oct with the PHP team's advance notice, and that date stands.2

The curves are Kaplan-Meier estimates with Greenwood intervals on a log-log scale, and the median's interval is where the band crosses one half. Shares have Wilson intervals. We checked the median three ways decided before looking at the data: first reports up to 15 Oct only (3 days, n = 56); without the single most frequent first publisher (2 days, n = 75); and without news organizations as witnesses, which didn't apply because there were none. Three more came out of reading the data: Asterism's dates as they stand (3 days), the PHP2Shell stories folded into one (3), and the suspected same-publisher pairs counted once (3). The results run from 2 to 3 days, so that range is the headline.

To check the clustering, we drew 20 corroborated stories at random and compared the first report with the second organization's. Of those, 18 described the same activity. Of the other two, one was the PHP2Shell story, whose misdated first report we corrected; in the other, both reports concern one CVE, but the first covers the fix and the second a later backport for older devices. The sample and our reading of each pair are in validation.csv, and every query is in queries.aql.

About the Data

As of
Window
19 Sep to 31 Oct 2026
Coverage since
Panel
183 sources reported in the first two weeks of the window, 196 in the last two; the data counted here come from 134 organizations
Marking
TLP:CLEAR
Left out
Undated reports, marketing and product news, round-ups (never clustered), publishers who opted out of AI use, and anything above TLP:CLEAR. Single reports that joined no story are outside the survival analysis.

This measures reporting, not activity. It counts what was published.

Null Sec sells Asterism, the platform these data come from.

Method: How Null Sec Counts

Data and Queries

The files behind every figure and number in this report, as published. Each SHA-256 lets you check you have the same bytes.

  • survival.csvThe data behind Fig. 1.2.7 KB · SHA-256 021fba30df95a797de20e6db8dc4b69893f02040377425c98ad14dbe3afe8891
  • shares.csvThe data behind Fig. 2.122 bytes · SHA-256 bd6ef4dc59079b88e320f1584cdd530000448f4cdce2ec01cde8d908a22d9b48
  • lags.csvThe data behind Fig. 3.905 bytes · SHA-256 f27c104d4a9b6ceb2b6a62f9d0dfe953449cded72b4945abab3f46f6e2710f12
  • weekly.csvThe data behind Fig. 4.349 bytes · SHA-256 1195fa832e5577702b20926b48400049f32b09ac7924160bd804573183198dc9
  • organizations.csvSupporting data.11.9 KB · SHA-256 4f8b8bfb6b7ae8ee2b52c23d8bce4b05742abe2c0e79e2a1b01fa52ac980d191
  • stories.csvSupporting data.6.0 KB · SHA-256 5f141bbdc17e9d5b6a48f81562a8cc761d2cd3d3a0101f7dea24c28955e408b8
  • story-sources.csvSupporting data.45.0 KB · SHA-256 c14c68633049665ff12137ec59ac2880f7ad4f5daed798cfa11c02a1ef9a276b
  • validation.csvSupporting data.8.7 KB · SHA-256 c64e1423439dd050a7337d95351a926f8edccb849f63324ae9ed2c32f2258c2c
  • queries.aqlThe exact queries, with their windows and the dates they ran.19.5 KB · SHA-256 3e0ecf9c9a8756a0e421622891df55070fd130dbaec806f5f9dd1105c4159f87
  • sources.csvEvery report cited or counted, with its publisher, date, URL and TLP.453 bytes · SHA-256 80e7538f923c0c566d6b5ce3a2c047bfd88def3704d0169770020ee2bd4948c6

References

  1. Arete, "Cyber Campfire: September Threat Trends & Insights", dated 15 Oct 2026 in Asterism. areteir.com/resources/cyber-campfire-september-threat-trends-insights ↑
  2. Blackpoint Cyber, "PHP2Shell: Critical PHP RCE CVE-2026-109618 & CVE-2026-109619", opened 20 Oct 2026. blackpointcyber.com/blog/php2shell-cve-2026-109618-cve-2026-109619/ ↑
TLP:CLEAR Share freely, subject to standard copyright rules.Corrections: none so far

Spot an error? Write to us and we'll fix it here, with a dated note.