ryuheimat3@gmail.com

ryuheimat3@gmail.com is an email address that 3 published sources report in connection with IT Worker Fraud activity, which public reporting attributes to North Korea (DPRK). It is cited here from Lazarus Group DPRK IT-Worker Registry (lazarus.group), Chollima Hunter and tayvano (lazarus-bluenoroff-research). The earliest of those reports is dated 2026-08-30 and the most recent 2026-10-18.

The reporting files it under the persona Ryuhei Matsuda, alongside 17 other identifiers attributed to the same identity. The persona page shows them together with any accounts, photographs and CV recorded under that name. A persona name is the one an account presented under, and may belong to an uninvolved person whose identity was taken.

email address IT Worker Fraud CURATED

First seen 2026-08-30 · last seen 2026-10-18

Sources

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09
  • Found on 24 September 2026 by searching GitHub's commit index for every personal address the lazarus.group registry gives for a persona, and keeping the accounts whose own repositories are committed with one. GitHub mints a noreply address from an account's immutable numeric id, in the form id+handle@users.noreply.github.com, so former handles below are a matter of record. github.com/jcking89 is account id 40835770, created on 4 July 2018, with 89 public repositories. Forty-nine commits in nineteen of them are signed ryuheimat3@gmail.com, an address lazarus.group and tayvano give for Ryuhei Matsuda, which GitHub attributes to github.com/ryuheimat, the account both list for the persona. They carry the author names ryuheimat, Ryuhei Matsuda, ryuhei and r2moon and are made on the day each repository was created, from cryptoExchange on 6 January 2021 and LendBorrow on 3 June 2021 to simple-univ3-integration on 6 July 2023; in all but one of the repositories read they are the only commits. An account whose repositories are opened with the persona's identity, over two and a half years, is the persona's second account or one it has push access to.
    github.com/jcking89 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-24
  • …Loom Network, Naos Finance, Raze Network, Sandclock, Shardeum, Paid Network, Hyperionx - ryuhei.eth - ryuheimat - ryuheimat3 - ryuheimat3@gmail.com - linkedin.com/in/ryuhei-matsuda - github.com/ryuheimat • [Archive](https://archive.ph/V5GsZ) - github.com/mono300genuine •…
    DPRK IT Workers — tayvano (lazarus-bluenoroff-research) · under “Ryuhei Matsuda” · published 2025-06-19 · pulled 2026-08-30

Find this indicator in the index, or see every email address this site holds under Email addresses in the browse listing.

Related indicators

Same persona record: Ryuhei Matsuda

Other identifiers the reporting files under the same persona; 8 of 17 are shown.

All 17 on the Ryuhei Matsuda page

Cited by the same report: lazarus.group/team/ryuhei-matsuda

Lazarus Group DPRK IT-Worker Registry (lazarus.group) lists 10 other indicators in this source. 2 are shown, chosen across types.

All 11 indicators from this source

Cited by the same report: github.com/jcking89

Chollima Hunter lists 1 other indicator in this source.

Cited by the same report: DPRK IT Workers

tayvano (lazarus-bluenoroff-research) lists 854 other indicators in this source. 1 are shown, chosen across types.

All 855 indicators from this source

Disclaimer An entry here is not proof of DPRK affiliation or wrongdoing. A listed name, account or address may belong to an uninvolved person, so each entry is a lead to verify independently. What inclusion means. See the sourcing methodology.