Lumiverse NexusSecurity Intelligence Platform
Nexus Threat Network

Real security activity. Real containment.

Privacy-preserving aggregate telemetry from active Nexus PRO protection. These counters reflect recorded security activity—not simulated dashboard numbers.

LIVE AGGREGATE Updated 4 min ago
SHARED INTELLIGENCE · LOCAL DECISIONS Network evidence adds context. Each site keeps the final protection decision local.

No public site list, raw IP feed or customer activity is exposed through this Pulse.

Threat Network + Nexus Intelligence

Shared activity shows the pressure. Shared intelligence helps recognize the behavior.

The public Pulse reports privacy-preserving aggregate security activity. Nexus Intelligence separately provides bounded attack-pattern context to participating licensed sites, while every final decision remains local.

Explore Nexus Intelligence →
THREAT NETWORK PULSELIVE AGGREGATE
HEADLINE WINDOWSince Sep 5
DATA MODELAggregate only
SIMULATED COUNTERSNone
REFRESHUpdated 4 min ago
Verified activity

What Nexus protection has actually recorded.

Headline totals use since sep 5 while the live charts remain rolling 24-hour views. Containment and observation stay separate.

SINCE SEP 5 · CONTAINMENT195.3K

Security actions contained

Recorded protection actions that contained request or commerce pressure.

CONTAINED
EARLY DEFENSE161K

Stopped before WordPress

Requests rejected by early protection before normal WordPress execution.

EARLY BLOCK
COMMERCE160.2K

WooCommerce pressure contained

Commerce-specific pressure or automated actions contained by Nexus.

COMMERCE DEFENSE
OBSERVED · CREDENTIAL PRESSURE5,180

Credential pressure observed

Meaningful distributed or repeated login-pressure signals. Ordinary mistyped passwords are not counted.

ENFORCED · LOGIN GUARD713

Login Guard restrictions

Temporary login restrictions or lockouts actually enforced by Nexus.

OBSERVED · NOT NECESSARILY BLOCKED49.9K

Reconnaissance signals observed

Security-relevant probing, enumeration and reconnaissance observations.

XML-RPC10.3K

XML-RPC restrictions

XML-RPC pressure or abuse restricted by Nexus protection layers.

24-hour containment

Protection activity over time.

Bars are real hourly aggregate counts. The red-lit peaks mark the busiest containment windows—not a different metric.

2026-09-19T13:00:00Z — 27 contained2026-09-19T14:00:00Z — 49 contained2026-09-19T15:00:00Z — 14 contained2026-09-19T16:00:00Z — 178 contained2026-09-19T17:00:00Z — 29 contained2026-09-19T18:00:00Z — 183 contained2026-09-19T19:00:00Z — 38 contained2026-09-19T20:00:00Z — 199 contained2026-09-19T21:00:00Z — 97 contained2026-09-19T22:00:00Z — 99 contained2026-09-19T23:00:00Z — 21 contained2026-09-20T00:00:00Z — 235 contained2026-09-20T01:00:00Z — 852 containedPeak activity — 8522026-09-20T02:00:00Z — 293 contained2026-09-20T03:00:00Z — 65 contained2026-09-20T04:00:00Z — 34 contained2026-09-20T05:00:00Z — 474 containedPeak activity — 4742026-09-20T06:00:00Z — 35 contained2026-09-20T07:00:00Z — 94 contained2026-09-20T08:00:00Z — 310 containedPeak activity — 3102026-09-20T09:00:00Z — 51 contained2026-09-20T10:00:00Z — 139 contained2026-09-20T11:00:00Z — 76 contained2026-09-20T12:00:00Z — 4 contained
24 hours agoNow
24-hour signal lanes

Where is Nexus seeing pressure—and where is it acting?

Independent counts, scaled against the highest lane. These categories can overlap and are not percentages of one whole.

Early defense1,085
WooCommerce pressure1,032
Credential pressure observed210
Login Guard restrictions64
Reconnaissance observed2,204
XML-RPC restrictions1,406
Observation layer

Reconnaissance over time.

Observed probing remains visually separate from containment. Credential pressure and reconnaissance do not become block counts unless Nexus actually enforces a restriction.

2026-09-19T13:00:00Z — 61 reconnaissance observations2026-09-19T14:00:00Z — 89 reconnaissance observations2026-09-19T15:00:00Z — 52 reconnaissance observations2026-09-19T16:00:00Z — 215 reconnaissance observations2026-09-19T17:00:00Z — 59 reconnaissance observations2026-09-19T18:00:00Z — 79 reconnaissance observations2026-09-19T19:00:00Z — 73 reconnaissance observations2026-09-19T20:00:00Z — 156 reconnaissance observations2026-09-19T21:00:00Z — 64 reconnaissance observations2026-09-19T22:00:00Z — 58 reconnaissance observations2026-09-19T23:00:00Z — 84 reconnaissance observations2026-09-20T00:00:00Z — 46 reconnaissance observations2026-09-20T01:00:00Z — 45 reconnaissance observations2026-09-20T02:00:00Z — 111 reconnaissance observations2026-09-20T03:00:00Z — 102 reconnaissance observations2026-09-20T04:00:00Z — 59 reconnaissance observations2026-09-20T05:00:00Z — 187 reconnaissance observations2026-09-20T06:00:00Z — 63 reconnaissance observations2026-09-20T07:00:00Z — 43 reconnaissance observations2026-09-20T08:00:00Z — 78 reconnaissance observations2026-09-20T09:00:00Z — 173 reconnaissance observations2026-09-20T10:00:00Z — 206 reconnaissance observations2026-09-20T11:00:00Z — 83 reconnaissance observations2026-09-20T12:00:00Z — 18 reconnaissance observations
24 hours agoNow
Telemetry history

Daily contained security activity.

History begins at the first real telemetry day. Nexus does not invent zero-filled pre-launch history to make the window look older.

Sep 5 — 1,076Sep 6 — 4,274Sep 7 — 4,246Sep 8 — 5,802Sep 9 — 3,039Sep 10 — 3,402Sep 11 — 5,662Sep 12 — 8,345Sep 13 — 5,927Sep 14 — 5,717Sep 15 — 4,552Sep 16 — 6,539Sep 17 — 87,936Sep 18 — 42,606Sep 19 — 3,467Sep 20 — 2,662
Since Sep 5Today
Verified period context

24-hour activity stays live and precise. Longer headline totals grow only from real daily telemetry, with 30-day comparison enabled after enough history exists.

24H CONTAINMENT3,596
7-DAY CONTAINMENT156.1K
SINCE SEP 5 · CONTAINED195.3K
SINCE SEP 5 · EARLY BLOCKS161K
SINCE SEP 5 · WOO PRESSURE160.2K
30-DAY COMPARISONBuilding history
How to read the Pulse

Action, observation and early containment are different things.

The page is deliberately strict about language. A large number is useful only when the label still describes what Nexus actually recorded.

Contained

Nexus actively restricted or neutralized activity. Red accents are reserved for real containment and high-pressure moments.

Stopped before WordPress

The request was rejected by an early protection layer before normal WordPress execution, reducing avoidable application work.

Observed

Reconnaissance and credential pressure that Nexus recorded as security-relevant. Observation does not automatically mean correlation, compromise or enforcement.

Privacy-preserving by design

Security counts travel. Customer activity does not.

Nexus PRO contributes compact aggregate security telemetry in background batches. The public Pulse receives only sanitized totals prepared by the Controller.

  • No customer content or order data
  • No usernames, cookies or request bodies
  • No public domains, site IDs or reporting-installation count
  • No public raw IP or per-site activity feed
01Nexus PROLocal security activity
→
02ControllerValidate & aggregate
→
03Static snapshotSanitized totals
→
04Public PulseCached presentation
Threat Network

Shared intelligence without surrendered control.

Participating Nexus installations contribute carefully selected security evidence and receive fresh network intelligence while enforcement remains local to each protected site.

Independent contributor context

Network observations are evaluated with contributor independence and freshness rather than treating raw report volume as consensus.

Asynchronous delivery

Qualifying evidence and aggregate telemetry are delivered outside visitor requests, with retry and back-pressure behavior designed to avoid slowing protected websites.

Local final verdict

Downloaded intelligence adds context to local Nexus decisions. A temporary network-service outage does not turn the cloud into a synchronous dependency.

Nexus PRO

Protect locally. Learn collectively.

Threat Network intelligence is included with an active Nexus PRO licence.

See plans & pricingExplore protection