TIA · HYDRA

Cyber Signal

A daily cut from public sources. You don't subscribe to it. It just gets published.
No account. No email address. No tracking.

TODAY'S CUT

15 items

← 2 Sep3 September 20264 Sep →ARCHIVE

◢ Daily 06:00 UTC

SEVEN DAYS

items per day

12Fri

12Sat

2Sun

11Mon

13Tue

15Wed

15Thu

IN THE WILD

9/ 15

items report exploitation — not proof of concept

WHAT DID NOT MAKE IT

99.2% of parsed records are not here.

▸▸▸

records parsed from the source feeds — before the time window and de-duplication

21 dropped by rule · 17 held by the daily cap · +3 pulled back from the agent-security lane (12 + 3) — items the daily cap held. They ship without an editorial rationale, because held items do not carry one. · config 8302303C — unchanged since 2026-09-02

The digest hands us counts, not the discarded items — so this shows how many and why, not which.

📦 NPM ECOSYSTEM

measured 2026-08-12 from public APIs, not quoted

02030405060708

July brought 4,084 new advisories for malicious npm packages. Other months run around 731 — July is a spike, not a trend.

All 8,189 of them, across seven months, are rated critical. Not one carries a computed CVSS score — there is nothing to score in a malicious package. It is not a flaw in the code, it is intent. Triage them by severity and every one is a tie.

But reach is distributed extremely unevenly. Of the 354 packages we could resolve, 67% have no dependents at all — their reach is zero. Among the rest the median multiplier is 1.95×, and 7% multiply thirtyfold or more. Highest measured case: engine.io has 118 direct dependents and reaches 15,865 through the tree. An average severity cannot see that spread at all.

Dependencies: a deps.dev v3alpha dependentCount measurement, SINGLE provider, no cross-check, window 2026-07. The package version is picked by a rule frozen BEFORE the run and BLIND to the measured value — the earlier method took the maximum across six versions, i.e. selected on the quantity it was meant to measure, and overstated the tail twofold. Amplification is undefined for packages with no dependents; those are reported separately as zero reach, not as a missing value. And advisories capture a fraction of malicious packages — this is the advisory denominator, not the malware denominator.

ATTENTION

7 6 2

SOURCES

The Hacker News7

BleepingComputer2

CISA Advisories2

Dark Reading2

SecurityWeek1

Attention classes are how much attention we gave an item. They are not severity verdicts.

Cyber Signal

TODAY'S CUT

SEVEN DAYS

IN THE WILD

WHAT DID NOT MAKE IT

📦 NPM ECOSYSTEM

ATTENTION

CATEGORIES

SOURCES

🎯CISA Adds Seven Exploited Flaws as Attackers Deploy Reverse Shells and Crypto Miners

🎯Attackers Exploit Two SonicWall SMA 1000 Zero-Days That May Form an Attack Chain

🔑Attackers Exploit Critical Switchvox Flaw to Deploy Reverse Shells Without Credentials

🎯CISA Adds Seven Known Exploited Vulnerabilities to Catalog

🎯SonicWall warns of actively exploited SMA1000 zero-day flaws

🤖Researchers Use Claude to Port Pre-Auth RCE Exploit From One PLC Model to Another

🎯SonicWall SMA 1000 Zero-Days Enable Unauthenticated RCE

🎯SonicWall Warns of Two SMA1000 Zero-Days Exploited in Attacks

🎯Researcher Releases FalconFlank PoC Showing Privilege Escalation in CrowdStrike Falcon

🩹Hackers exploit Sangoma Switchvox flaw to deploy reverse shells

🤖Trump administration sides with OpenAI in lawsuit against New York Times

🟡Communicating Under Pressure: Best Practices for Service Providers

🤖Malicious .git Configs Can Make Claude, Codex, Cursor, and Other AI Agents Run Attacker Code

🤖How to Secure Enterprise AI: From Adoption to Incident Readiness

🤖AI’s Vulnerability Surge May Be More Manageable Than First Feared