GDELT CloudGDELT Cloud
Connected Situation / Through 2026-09-18

Fraud Targeting Russian Pensioners Through Fake Elderly Day Payments

stories
1
events
1
entities
38
connections
1
Retained edition
Evidence so far on 2026-09-18 UTC · updated 2026-09-18 07:23 UTC · analysis as of 2026-09-17 16:23 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

The retained evidence concerns reported fraud in which scammers targeted Russian pensioners with fake Elderly Day payments. The evidence is anchored by one Story and its linked coded Event on 2026-09-17.

Footnotes[1][2]
Assessment

The core situation is reported fraud targeting Russian pensioners in Russia. The coded Event has confidence 0.9, significance 0.2785 and magnitude 2; these are event-level metrics, not a Situation-wide risk assessment.

Footnotes[2][9]

Explanation originally captured 2026-09-17 · Evidence through 2026-09-18 UTC · Source edition sed_2384a5b683b038a7e05bde3c2399252b

What informs this explanation
  • Complete retained Story and Event membership
  • Daily reporting and coded-occurrence time steps
  • Event taxonomies, metrics, units, and denominators
  • Canonical Entities and recorded actor/target bindings
  • Typed reporting, membership, and incident edges
  • Changes against the preceding retained edition
  • Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative

Evidence in numbers

This retained edition
  • Scope

    A 1-day Situation represented by 1 coded Event carried across 1 member Story.

  • Coded activity

    The coded activity is led by CR05 · Fraud or Financial Crime (1).

  • Prominent subjects

    🇷🇺Russia is prominent in the retained actor and relationship evidence.

  • Entity coverage

    38 canonical Entities are linked to this edition.

Metric coverage. 1 coded Events · 1 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude2
min 2max 2
1 measured
Systemic importance0.08
min 0.08max 0.08
1 measured
Propagation potential0.29
min 0.29max 0.29
1 measured
Market sensitivity0.05
min 0.05max 0.05
1 measured

Dot = mean · shaded span = observed range · position uses each metric’s defined scale.

All 6 scores, distributions & definitions

How the coder scored the full retained Event set

1 coded event — 1 CAMEO+

  • Significance · 10.28
    min 0.28max 0.28
  • Magnitude · 12
    min 2max 2
  • Systemic · 10.08
    min 0.08max 0.08
  • Propagation · 10.29
    min 0.29max 0.29
  • Market · 10.05
    min 0.05max 0.05
  • Confidence · 10.9
    min 0.9max 0.9

No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 1 sit outside POLITICAL, where Goldstein and quad class are undefined.

Significance

1 measured / 1 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 1 events

Magnitude

1 measured / 1 eligible · 0 missing · 0 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across all 1 events — every one of them CAMEO+

Systemic

1 measured / 1 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 1 events — every one of them CAMEO+

Propagation

1 measured / 1 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 1 events — every one of them CAMEO+

Market

1 measured / 1 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 1 events — every one of them CAMEO+

Confidence

1 measured / 1 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 1 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

Day by day1 reporting day · click a day to open or close it

2026-09-17analystlatest

Reported and coded evidence on 2026-09-17

The Story is dated 2026-09-17 and reports the fake-payment fraud; the coded Event also has occurred_on 2026-09-17 and describes the same targeting of Russian pensioners. The timeline packet retains this reporting and coded occurrence as the basis for the as-of explanation.

Scammers target Russian pensioners with fake Elderly Day paymentsScammers defraud Russian pensioners with fake Elderly Day payments
1
Stories
1
Events
620
articles
The lay of the land

Situation timeline

Threads
All 1 dayarticlesstoriesevents
Loading Situation timeline…

What kind of event · 1 coded type

over 1 coded event on this edition

  • Crime1
    • CR05 · Fraud or Financial Crime1

Countries · where it happened

Countries · who is acting

Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystFake Elderly Day payment fraud

    This is the core thread because the retained Story and coded Event describe the same fraud claim and identify scammers as targeting Russian pensioners.

    This is the core thread because the retained Story and coded Event describe the same fraud claim and identify scammers as targeting Russian pensioners.

    Footnotes[1][2]

Key actors

    Key Events

    1. contextAnalystScammers target Russian pensioners with fake Elderly Day payments

      The Event records fraud or financial crime involving scammers and Russian pensioners in Russia on 2026-09-17. The supplied Event contains no canonical actor bindings, so the named source and target are not selected as Entity players.

      The Event records fraud or financial crime involving scammers and Russian pensioners in Russia on 2026-09-17. The supplied Event contains no canonical actor bindings, so the named source and target are not selected as Entity players.

      Footnotes[2]

    Notable connections

    Evidenced relationships involving significant participants beyond the central cast.

    1. The Story supports the coded Event describing fake Elderly Day payments targeting Russian pensioners. · reporting linkAnalystScammers defraud Russian pensioners with fake Elderly Day payments → Scammers target Russian pensioners with fake Elderly Day payments

      The Story lists the Event as linked, and the Event lists the Story in its story_ids.

      The Story lists the Event as linked, and the Event lists the Story in its story_ids.

      Footnotes[1][2]
    2. The Social Fund of Russia is mentioned in the Story. · reporting linkAnalystSocial Fund of Russia → Scammers defraud Russian pensioners with fake Elderly Day payments

      The Entity record lists the Social Fund of Russia as a mention in the Story; this provides limited context for the reporting and does not establish Event participation.

      The Entity record lists the Social Fund of Russia as a mention in the Story; this provides limited context for the reporting and does not establish Event participation.

      Footnotes[3][1]
    3. The Social Fund of Russia is mentioned in the Story under an alternate retained classification. · reporting linkAnalystSocial Fund of Russia → Scammers defraud Russian pensioners with fake Elderly Day payments

      The Entity record lists the Social Fund of Russia as a mention in the Story under a separate retained classification; this provides limited context for the reporting and does not establish Event participation.

      The Entity record lists the Social Fund of Russia as a mention in the Story under a separate retained classification; this provides limited context for the reporting and does not establish Event participation.

      Footnotes[6][1]
    4. The Ministry of Internal Affairs of Russia is mentioned in the Story. · reporting linkAnalystMinistry of Internal Affairs of Russia → Scammers defraud Russian pensioners with fake Elderly Day payments

      The Entity record lists the Ministry of Internal Affairs of Russia as a mention in the Story; this provides limited context for the reporting and does not establish Event participation.

      The Entity record lists the Ministry of Internal Affairs of Russia as a mention in the Story; this provides limited context for the reporting and does not establish Event participation.

      Footnotes[8][1]
    5. People's Front is mentioned in the Story. · reporting linkAnalystPeople's Front → Scammers defraud Russian pensioners with fake Elderly Day payments

      The Entity record lists People's Front as a mention in the Story; this provides limited context for the reporting and does not establish Event participation.

      The Entity record lists People's Front as a mention in the Story; this provides limited context for the reporting and does not establish Event participation.

      Footnotes[7][1]

    Current related Situations

    Explore all →

    Finding connected developments…

    Compared with currently maintained Situation membership; this list is not part of the retained edition above.

    How a Situation is put together1 Stories · 1 Events · 1 membership connections · 39 graph edges

    A retained time step

    This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.

    Stories, Events, and cast

    Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 38 canonical people and organizations linked to the retained evidence.

    Typed connections

    Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.

    Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.