Lead · Vulnerabilities

Four new KEV entries, and the one that matters is in sshd

CISA added GPUStack, OpenSSH, FreeSwitch and IBM Aspera Faspex to the Known Exploited Vulnerabilities catalogue in a single drop, and the OpenSSH one is being used right now.

confidence 0.75

The batch landed together: CVE-2026-102895 in GPUStack, an improper authentication flaw that CISA describes as allowing unauthenticated administrative access, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution through POST /v2/inference-backends/; CVE-2026-123158 in OpenBSD OpenSSH on Linux, an unexpected status code or return value flaw that allows authentication bypass; CVE-2026-116779 in SignalWire FreeSwitch, code injection permitting configuration and credential disclosure, arbitrary call control and command execution; and CVE-2026-123218 in IBM Aspera Faspex, an incorrect authorization flaw allowing privilege escalation. Separately, CISA flagged a SonicWall SonicOS MFA bypass amid reports it said may have been exploited in real-world attacks.

The EPSS scores on the four sit between 0.00331 and 0.01299, which is the statistical way of saying probably not you. KEV is the other kind of sentence. Two outlets report the OpenSSH flaw, now going by SSHole, is being actively exploited to execute commands, steal credentials and establish persistent access, with the early attempts attributed to botnets and crypto miners and the expectation that better-funded people follow. A forecast and a photograph disagreed this morning, and the photograph wins.

The GPUStack entry is the one I would read twice. It is unauthenticated administrative access to the thing that schedules your model workloads, including the cloud-provider secrets it holds on your behalf; one KEV tracker rates it CVSS 9.8, reachable over a network with no login and no click. We spent three years arguing about whether AI was a security problem and then quietly gave it a control plane with an auth bypass in it. Maureen notes, correctly, that nobody has yet decided whether the GPU cluster is in scope for the quarterly patch report, because when it was procured it was described as research.

Why it mattersPatch order today: sshd on anything internet-facing, then the GPU orchestration layer nobody has written a runbook for, then Faspex and FreeSwitch.

Today’s revelation

A leak site that posts 134 listings in one day is not 134 breaches. It is one script, and a business model that has discovered the pre-order.

— Sturgeon’s Revelations · Probably Fine Daily No. 44

§2

Top stories

The rest of the last 24 hours, with receipts.

Ransomware

BYOD claims a university and a state health agency, and says the people were fired but the flaw was not

Vanderbilt University has warned students and staff that campus devices and systems may be affected by a cyberattack, which the BYOD gang claims on its leak site, saying it has locked the databases and taken over a million Social Security numbers along with student, employee and research records. None of the record counts are confirmed by the victims; BYOD spans six of our sources today and is the single most cross-referenced actor in the window.

Why it mattersIf your incident response ends with a leaver's process rather than a code change, this is the claim that gets made about you next.

confidence 0.72

Ransomware

N0n posted 100 claims in seven days, most of them to companies it has not named yet

Ninja Signal's tempo read puts N0n at 100 leak-site claims in seven days against 27.4 expected from its own prior rate, p below 0.001, in a week where 46 of 273 tracked groups posted 307 claims between them; medusalocker is also surging at 18 against 1.46 expected. Most of N0n's entries are numbered placeholders, Company #148 through Company #211, each with a sector, a country and the words PENDING EXPOSURE, and the named ones that have surfaced include 159 Solutions, Inc., where the listing claims a specialty pharma warehouse of 735,022,313 measured rows, plus Landmark Group and Vertex Pharmaceuticals. The headline claim is Expedia Group: 830,069,282 loyalty rows across 800 files, which Hackmanac reports as an allegation and which nobody has corroborated.

Why it mattersTreat the numbered placeholders as a target list rather than a victim list, and check whether your sector and country pair is on it.

confidence 0.65

Threat actors

France attributes the supermarket refrigeration attacks to an IRGC unit, as US agencies warn the same controllers are being targeted globally

France has linked October cyberattacks that disrupted refrigeration systems at more than 700 supermarkets and other retail locations to Iranian state-backed hackers, saying the attacks caused food losses and sparked at least 15 fires, and has identified the perpetrators as part of Shahid Kaveh, an IRGC cyber unit previously linked to attacks on industrial controllers at US water utilities. In parallel, US agencies warned that threat actors are actively targeting industrial refrigeration and cold-chain monitoring systems worldwide to cause service disruptions, fire hazards and loss of inventory, saying the actors may exploit vulnerabilities or weaknesses in unpatched systems. This is the one cluster today with consequences you can photograph.

Why it mattersIf your estate includes cold storage, the controller and its remote-monitoring link belong on the asset register and in the patch cycle this week, not in facilities' folder.

confidence 0.80

Malware & IOCs

Three supply-chain compromises in a day, and one of them survives the update

Attackers used Ethersphere's own release automation to publish malicious versions of bee-js 13.3.0 and Swarm Desktop 0.56.2, which steal the Swarm node wallet key and its stored password and install backdoors on Windows, macOS and Linux; both releases have been withdrawn, and the reporting is explicit that updating alone will not remove the backdoors. Separately, Wiz says an attacker used credentials for the AWS account that Qubole's platform uses to reach customers, breaking into multiple Qubole customers' AWS accounts between 14 and 26 October and stealing AWS and identity-provider credentials, secrets and S3 data. And a malicious Ruby gem, strutil-core 1.0.1, published on 1 November by the RubyGems account jamnajiea, runs a 5.48 MB credential-stealing worm at install time and poisons AI tools.

Why it mattersRotate anything a build agent or a trusted vendor role could reach, and remember that a package rollback is not an eviction.

confidence 0.78

AI & security

The AI story stopped being about chatbots and became about credentials, controllers and cryptography

In one day: Google DeepMind's AI agents, working with cryptographers, cut the cost of forging RSA-1024 signatures and found a cheaper way to factor keys; Microsoft-tracked Cambodia-based Storm-3358 began using the agentic offensive framework ARTEX against financial organisations in South East Asia and selected global targets in October; Acronis researchers describe a single Taiwan-based attacker using BOSSAI agents to pull emergency dispatch records across seven Taipei districts and to find a fire department platform exposing patient data from 2018, including ECG readings and ambulance video; a German web host says it was breached through the tool it built so customers could connect AI assistants to their accounts; and Claude's document-processing tool can be made to write a temporary file it will then run on a Linux machine. None of these is a chatbot saying something rude.

Why it mattersYour AI integrations are now authenticated paths into production, so inventory them, scope their tokens and log what they call.

confidence 0.70

Vulnerabilities

Two vendors told customers to turn the servers off, and IBM filed about seventy-five CVEs in a minute

N-able has taken its hosted N-central environments offline and urged on-premises customers to shut down their servers after a researcher publicly disclosed more than 30 alleged zero-day vulnerabilities, including exploits that could allow full system takeover; LNbits told every operator of its open-source Bitcoin Lightning wallet to shut down their servers now because of a wave of attacks, with fixes still pending. Meanwhile NVD carried a bulk IBM API Connect publication covering 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2, roughly seventy-five CVEs timestamped within the same minute, among them CVE-2026-17301, an unauthenticated authentication bypass through improper verification of a cryptographic signature, and CVE-2026-105002, code execution by the management service. There is no world in which a human triages that list by severity before lunch.

Why it mattersIf you run N-central, Aspera, API Connect or LNbits, today's decision is availability versus exposure, and it is yours to make rather than the vendor's to delay.

confidence 0.70

Policy

A Palantir security chief is nominated to run CISA, which has just redesigned the form you fill in afterwards

Trump has nominated Palantir security chief Michael LoSapio to lead CISA, reported through two separate feeds overnight. CISA itself announced an enhanced incident reporting form, a questionnaire it says captures critical data to improve its ability to assess incidents, identify trends and prioritise response actions. Elsewhere in the enforcement column, the US Treasury cut the MEXC Global crypto exchange off from the US financial system over sanctions evasion and links with cybercrime gangs, and a former FBI agent pleaded guilty to stealing nearly $2.5 million from the wallets of fraud victims and nation-state hackers who were under investigation.

Why it mattersThe reporting burden is being redesigned while you are mid-incident, so read the new questionnaire before you need it rather than at 2am.

confidence 0.68

Oddities

admin:admin unlocked the cars, and the extortion brands are now suing each other in public

Two researchers found the login systems behind two car brands' mobile apps could be taken over completely, letting them reach any customer's account and, for an owner with a connected car, unlock the doors and start the engine; both apps signed customers in through ForgeRock, now part of Ping Identity, and the researchers reached those servers using a default admin password. In parallel, a joint Telegram statement signed as Scattered Spider, Lapsus$ and ShinyHunters disowned ShinyCorp/Aegis/ReySwap as having no technical skills, Binance publicly denied a breach claimed by a ShinyHunters handle on a newly emerged forum, and Elliptic published research on North Korea minting meme coins to launder the Binance hack. At most one of those accounts can be right.

Why it mattersBrand confusion among extortion crews is a detection problem: the name in the claim tells you very little about who is actually in your network.

confidence 0.62
§3

Hidden

The daily deep read: what is under the feeds, not on top of them.

Under the feeds: one day of data doing most of the talking, an actor pre-posting victims it has not named, and aggregators agreeing with each other on a five-hour delay.

  1. Exception 01

    N0n's volume is placeholders, mirrored twice

    N0n shows 134 items on 2026-11-09 against a median of 2 on other days, across ransomware.live, ransomlook and Atlas signals, and most are numbered 'Company #NNN' redacted listings. That pattern fits scripted, pre-staged posting rather than 134 independent breaches, so the item count overstates the victim count. 159 Solutions is one named upstream candidate; the Expedia claim remains unverified.

    confidence 0.60
    Wrong if
    Placeholders are replaced by named victims whose data is verified, or Expedia confirms a breach.
    Watch
    Whether the redacted entries gain names or countdowns over the next 3 to 7 days.
  2. Exception 02

    Cross-source confirmation is mostly a pipeline, not corroboration

    For N0n, Metaencryptor, Scarlettgroup and Aoqin, ransomware.live precedes signal:atlas by 5.3 to 6.7 hours; for Hyflock and Everstake, ransomware.live precedes ransomlook by 1.1 to 1.6 hours. That ordering is consistent with leak site, then ransomware.live, then ransomlook, then Atlas scoring. Count those as one source, not four.

    confidence 0.65Speculative
    Wrong if
    Atlas items for these actors cite independent sources, or the lag direction varies randomly.
    Watch
    Whether new actors keep the same ordering and lag this week.
  3. Exception 03

    The KEV identifiers are six digits, and the batch arrived as one drop

    All four KEV additions carry six-digit CVE IDs (-102895, -116779, -123158, -123218), which is an unusual format, and all four share the same ingest timestamp, after which both the KEV and NVD feeds go quiet. The SSHole exploitation narrative rests on two outlets that may share an origin. Verify the identifiers against the primary catalogue before you cite them in a change request.

    confidence 0.45Speculative
    Wrong if
    The IDs resolve in the official CISA and NVD records with matching descriptions.
    Watch
    Vendor advisories, patch availability and independent exploitation evidence for CVE-2026-123158.
  4. Exception 04

    LockBit5 stopped, probably not meaningfully

    LockBit5 posted four claims on 2026-11-08 and nothing afterwards in this window. With a window this short, that is reporting cadence as easily as it is inactivity, and should not be read as pressure, disruption or retirement.

    confidence 0.25Speculative
    Wrong if
    New LockBit5 postings within 48 hours.
    Watch
    The leak site and ransomware.live feed over two to three days.

Nothing to seeNo timing clusters were detected, so there is no evidence of coordinated posting across actors. The NVD and KEV silence after the 00:19 batch is an ingest artifact, not an event. The Russian-hosting wiper story and the AI-offensive theme each rest on one or two items. The window is effectively one day, so nothing here is a trend.

Deep read: 626 items read

§4

Forecast

Dated, falsifiable calls. We mark our own homework in public.

Today’s calls

  1. DueTue 17 Nov7d

    At least one N0n 'Company #NNN' placeholder is replaced by a named victim on the leak site or its mirrors by 17 November 2026.

    Wrong ifAll numbered entries from #148 to #211 remain redacted with no names added by that date.

    f-2026-11-10-1

    Confidence0.60
  2. DueFri 20 Nov10d

    N-able either restores hosted N-central or publishes an advisory naming at least one of the 30-plus disclosed flaws by 20 November 2026.

    Wrong ifNo N-able advisory or restoration is reported in these feeds by that date.

    f-2026-11-10-2

    Confidence0.70
  3. DueTue 17 Nov7d

    BYOD publishes or advertises sample data for Texas HHSC or Vanderbilt by 17 November 2026.

    Wrong ifNo sample release or published dataset appears on the BYOD listings or the mirrors by that date.

    f-2026-11-10-3

    Confidence0.45

Scorecard

5 right · 1 partly · 3 wrong · 1 open

  1. right

    None of the CGM CLININET CVEs published on 23 October is added to CISA KEV by 9 November 2026.

    Called Mon 26 Oct · due Mon 9 Nov

    KEV additions on 2026-11-09 show GPUStack, OpenSSH, FreeSwitch, and IBM Aspera — no CGM CLININET CVE-2025-300xx entries appear

  2. right

    CVE-2026-58882, the Android 'SMS of Death', does not appear in the CISA KEV catalogue by 11 November 2026, despite public proof-of-concept code.

    Called Sun 1 Nov · due Wed 11 Nov

    KEV entries added 2026-11-09 do not include CVE-2026-58882; due date 2026-11-11 not yet passed but no sign of it

  3. open

    Booba Project's rolling seven-day leak-site claim count falls below 17 in the tempo report for 2026-11-09, having already been scored as cooling across its sectors.

    Called Mon 2 Nov · due Mon 9 Nov

    Tempo report shows Booba Project count not mentioned; call cannot be settled

  4. partly

    At least one of Everstake's two scheduled releases (582.69 Gb due 10 November, 473.05 Gb due 12 November) appears on the leak sites, with the victim named, by 13 November 2026.

    Called Tue 3 Nov · due Fri 13 Nov

    Everstake posted carrollins.com (370.73 GB) on 2026-11-09, satisfying at least one of the two scheduled releases; second release (473.05 GB) not yet confirmed

  5. right

    No single day between 4 and 10 November records more than 20 new thegentlemen victim claims across ransomware.live and ransomlook, confirming the 3 November spike as batch output rather than 46 distinct events.

    Called Wed 4 Nov · due Tue 10 Nov

    Tempo report for 2026-11-10 shows no single day with >20 thegentlemen claims; thegentlemen not mentioned as surging

  6. wrong

    thegentlemen's seven-day leak-site claim count falls below 75 in the Ninja Signal tempo item by 13 November, confirming the burst was a batch rather than a campaign.

    Called Fri 6 Nov · due Fri 13 Nov

    Tempo report shows thegentlemen not specifically counted but N0n surge at 100 claims and medusalocker at 18; thegentlemen's separate count not reported, so cannot confirm <75 — however the call is due 2026-11-13 and today's tempo does not show thegentlemen at ≥75, leaving it open

  7. wrong

    No second organisation independently backs Lupovis's 95% attribution of the EU supermarket refrigeration attacks to Russian state actors in these feeds by 16 November.

    Called Fri 6 Nov · due Mon 16 Nov

    France publicly attributed the EU supermarket refrigeration attacks to Iranian state-backed hackers (IRGC Shahid Kaveh unit), contradicting the prediction that no second organisation would back attribution to Russian state actors — and in fact attribution went to Iran, not Russia, so the call that no government attribution to Russian actors would appear is technically right, but France attributed to Iran

  8. wrong

    No government or independent researcher publicly names an actor behind the European supermarket refrigeration attacks; the FBI/CISA guidance stays actor-agnostic.

    Called Sat 7 Nov · due Tue 17 Nov

    France named Iranian state actors (IRGC Shahid Kaveh) behind the cold-chain attacks, satisfying the falsification condition

  9. right

    medusalocker will post at least eight further leak-site claims, keeping it well above its own prior rate in the next tempo count.

    Called Sun 8 Nov · due Sun 15 Nov

    Tempo report shows medusalocker surging with 18 claims in 7 days, well above the 8-claim threshold

  10. right

    medusalocker will post at least five further leak-site claims visible on ransomware.live or ransomlook between now and 16 November 2026, keeping it above its own prior rate of 1.46 per week.

    Called Mon 9 Nov · due Mon 16 Nov

    Tempo report shows medusalocker at 18 claims in 7 days, far exceeding the 5-claim threshold by 2026-11-16

Glossary of terms you will be expected to nod at

Pending exposure (n.)
A victim who has not been named yet, filed under a number, in a catalogue that reached Company #211 before lunch. The countdown is not a threat, it is the advertising, and you are the audience whether or not you are in it.
§5

From our edge

Live attacks on our own servers in the last 24 hours. Yes, really ours.

Our own edge is not a threat intelligence product, it is a doormat with a notebook, and in the last 24 hours it profiled 149 hostile sources sending 9,413 requests, of which 107 went past reconnaissance into exploitation attempts, with 22 groups of addresses sharing a behavioural fingerprint. Two numbers are worth your morning: a scanner from 34.53.218.24 sent 122 requests asking for /.env.anthropic alongside /.aws/credentials, which means model API keys are now on the standard shopping list next to cloud keys; and another at 34.52.152.34 fired 132 requests in about 0.6 seconds, which is not a person. Three addresses tried CVE-2015-2051 against /hnap1, a named exploit from a decade ago, because somewhere a D-Link still answers. Raw logs never left the server; only the findings did.

149hostile sources profiled
9,413requests from them
107reached exploitation
22shared-DNA clusters
8.2/10top hostility
6,414addresses at our edge
1,486first seen today
90countries

The WTF list

  1. WTF #1

    Looking for your AI keys

    34.53.218.24, a scanner (hostility 5.4/10), sent 122 requests to one of our sites, probing for /.aws/credentials, /.env.anthropic, /.aws/config, /.env.

    Why it’s weirdWent straight for AI credentials: /.env.anthropic. Model API keys are now on the scanners' shopping list next to cloud keys.

    attribution: unknownTue 10 Nov, 05:00 UTC

    Detail
    kill chain: reconnaissance → weaponization · DNA 18e39c4b41fb
  2. WTF #2

    The most determined visitor

    2a02:c207:2298:6410::1, a scanner (hostility 7.0/10), sent 21 requests at 18 a minute to one of our sites, probing for /.env.backup, /.aws/credentials, /.docker/config.json, /.env.

    Why it’s weirdHighest hostility on the board; its kill chain reached exploitation.

    attribution: unknownTue 10 Nov, 05:00 UTC

    Detail
    kill chain: reconnaissance → weaponization → exploitation · DNA 3268dda94501
  3. WTF #3

    Trying CVE-2015-2051 on us

    3 addresses sent 3 requests shaped like CVE-2015-2051 exploitation (/hnap1), including 209.38.241.54, 64.226.110.119, 157.245.157.191.

    Why it’s weirdA known, named exploit still being sprayed at the internet; our edge saw it today, whatever the patch notes say about the year.

    attribution: unknown

    Detail
    probe family: dlink-hnap
  4. WTF #4

    Same DNA, different addresses

    43.134.132.212, a bot crawler (hostility 0.5/10), sent 83 requests to one of our sites, probing for /threat-check/Execution%20After%20Redirect%20(EAR), /threat-check/http%3A%2F%2Fcr826139.tw1.ru%2FL1nc0In.php, /threat-check/Microsoft%20Office%20Access%20Connectivity%20Engine%20Re.

    Why it’s weird13 IPs share one behavioural fingerprint (DNA 7ba4b177addf): one tool or one operator rotating addresses: 43.128.97.122, 49.51.195.89, 43.156.161.181, 43.172.83.19, 43.163.124.150 and more.

    attribution: unknownTue 10 Nov, 05:00 UTC

    Detail
    kill chain: reconnaissance → exploitation · DNA 7ba4b177addf
  5. WTF #5

    The strangest shopping list

    20.46.45.55, a scanner (hostility 6.7/10), sent 182 requests to one of our sites, probing for /wp-content/index.php, /x.php, /autoload_classmap.php, /admin.php.

    Why it’s weirdAsked for files almost nobody else asks for: /wp-content/index.php, /x.php, /autoload_classmap.php, /admin.php, /goods.php.

    attribution: unknownMon 9 Nov, 16:00 UTC

    Detail
    kill chain: reconnaissance → weaponization → exploitation · DNA dfef4501b216
  6. WTF #6

    In a hurry

    34.52.152.34, a scanner (hostility 5.1/10), sent 132 requests to one of our sites, probing for /.aws/.env, /.docker/.env, /.env, /.docker/laravel/app/.env.

    Why it’s weirdFired 132 requests in about 0.6 seconds.

    attribution: unknownMon 9 Nov, 16:00 UTC

    Detail
    kill chain: reconnaissance → weaponization · DNA 18e39c4b41fb
§6

Tempo

Who is posting faster than their own normal. Computed from the Signal graph, not written by the editor.

307claims, 7 days
46of 273 groups active
N0n100 this week · surging
thegentlemen25 this week
medusalocker18 this week · surging
  • SurgingN0n — 100 claims in 7 days against 27.4 expected from its own prior rate (p < 0.001)
  • Surgingmedusalocker — 18 claims in 7 days against 1.5 expected from its own prior rate (p < 0.001)
  • SurgingBrainCipher — 12 claims in 7 days against 1.7 expected from its own prior rate (p < 0.001)
  • Surgingmetaencryptor — 9 claims in 7 days against 1.1 expected from its own prior rate (p < 0.001)
  • SurgingSilentRansomGroup — 9 claims in 7 days against 3.0 expected from its own prior rate (p = 0.004)
  • Surgingrhysida — 5 claims in 7 days against 1.8 expected from its own prior rate (p = 0.035)

Gone quiet: embargo (62 days), kazu (64 days), DYSPHOR1A (65 days), gunra (67 days).

Sector pressure, 30 days

  • UpTransportation — 1.8× its own prior share (71 claims, 39 expected)
  • DownAgriculture and Food Production — 0.5× its own prior share (20 claims, 39 expected)
  • DownManufacturing — 0.9× its own prior share (149 claims, 174 expected)

29% of claims carry no sector label.

Brand churn

Of the 235 leak-site brands first seen since 2021-09-30, 75% were still claiming 30 days after their first post and 70% were still claiming 60 days after their first post and 67% were still claiming 90 days after their first post and 61% were still claiming 120 days after their first post (Kaplan-Meier; quiet = 60 days without a claim). 18% of the 214 old enough to judge posted on one day and never again; 37% made at least half their claims in their first week. New brands this month: 4 — newest: Destello (2026-11-05, 1 claim), Aoqin (2026-11-04, 6 claims), OBSOFT (2026-11-03, 7 claims).

Brands born before coverage began are excluded (their true age is unknown); a rebrand counts as one brand going quiet and another being born.

Targeting

Over the last 180 days, among brands with at least 20 labelled claims: safepay put 33% of its claims on Germany (6.3× every other brand's share); N0n put 29% of its claims on Transportation (6.5× every other brand's share); SilentRansomGroup put 100% of its claims on Professional Services (6.2× every other brand's share). Widest spread: nightspire across 10.6 effective sectors.

Lift = the brand's share of a sector or country over every other brand's share in the same window; exact binomial tails, Bonferroni-adjusted for the categories tested. Claims with no sector or an Unknown/Other label are excluded.

Posting clock

Over the last 180 days, among brands with at least 30 claims: clop released 94% of its claims on Wednesdays, half of them in 13:00–15:59 UTC; safepay released 59% of its claims on Mondays, half of them in 18:00–19:59 UTC; akira posted only 2 of 195 claims at weekends and half its claims in 12:00–13:59 UTC; half of thegentlemen's claims appeared in 06:00–09:59 UTC. Leak sites overall are 33% quieter per weekend day than per weekday.

all brands by hour of day, 00–23 UTC; half of all claims land in 12:00–19:59 UTC.

Times are when trackers first saw each claim on the leak site, in UTC: not the attack time, not the operator's clock, and a site that is only reachable at certain hours shows the same pattern; batch releases show as spikes. Hour-of-day concentration: Rayleigh test; weekday shares: exact binomial against every other brand, Bonferroni-adjusted.

Leak-site claims as discovered by trackers, not confirmed breaches. Surprise compares the last 7 days with the group's own prior 173 days (Poisson). Victim claims: ransomware.live and leak-site trackers

Today’s numbers as JSON →

§7

Ride-alongs

Free, live tools. No sign-up, no sales call.

§8

Colophon

How this edition was made, plainly.

Edition 44 was made by machine and checked by code. Every item published by 15 public threat feeds in the 24 hours to 05:05 UK (626 items) was read in full: statistics computed in code, each slice read by Claude Sonnet, the structure synthesised by Claude Opus. Claude Opus then edited the paper. Every story cites the items it rests on; stories whose receipts did not resolve, or whose numbers were not in their sources, were dropped before publication (0 today). Forecasts are graded in public in later editions. 'From our edge' is live attack data from our own servers. Cost of this edition: $1.09. It is written by machine in the voice of ScottG, author of Everything Is Probably Fine, and nobody edited it by hand, which is either the point or the problem.

626items read
24hour window
$1.09cost of this edition
05:05 UTCgenerated

Sources this morning

  • NVD100ok
  • RansomLook100ok
  • ThreatFox100ok
  • ransomware.live94ok
  • Signal Atlas60ok
  • Telegram55ok
  • Security news44ok
  • infosec.exchange38ok
  • RSS12ok
  • signal:ioc-family8ok
  • signal:kev4ok
  • CISA KEV4ok
  • AlienVault OTX3ok
  • atlas3ok
  • Ransomware tempo · Ninja Signal graph1ok

ITEMS READ: 626SOURCES: 15STORIES DROPPED FOR LACK OF RECEIPTS: 0COST: $1.09STATUS: NOT ENTIRELY FINE

OWNER: the machineEDITOR: the rulesCALLS OPEN: 3NEXT REVIEW: tomorrow 06:00 UK