Tom Cupples

Tom Cupples is an alias that one published source reports in connection with IT Worker Fraud activity, which public reporting attributes to North Korea (DPRK). It is cited here from Cookie Connoisseur (@browsercookies). The report is dated 2025-05-28.

The reporting files it under the persona Thomas Ray Cupples, alongside 4 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.

alias IT Worker Fraud RESEARCHER POST

First seen 2025-05-28 · last seen 2025-05-28

Source

  • The post consists of the single word DPRK and this one image: a LinkedIn profile under the name Thomas (Tom) Ray Cupples, headlined as a senior software engineer in JS, TS, Python, C# and machine learning for healthcare software, located in Yuma, Tennessee, with 80 connections and a University of Tennessee Knoxville entry. A one-word caption is the thinnest assertion anything in this file rests on, and it is recorded as the researcher's, with the text quoted here so a reader can weigh it for themselves.
    x.com/browsercookies/status/1927861180217045474 — Cookie Connoisseur (@browsercookies) · under “Thomas Ray Cupples / Tom Cupples” · published 2025-05-28 · pulled 2026-08-30

Find this indicator in the index, or see every alias this site holds under Aliases in the browse listing.

Related indicators

Same persona record: Thomas Ray Cupples

Other identifiers the reporting files under the same persona; 3 of 4 are shown.

All 4 on the Thomas Ray Cupples page

Cited by the same report: x.com/browsercookies/status/1927861180217045474

Cookie Connoisseur (@browsercookies) lists 1 other indicator in 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.