The Record

The Hooman Asbaghi Case

A filing is not a verdict. Nothing on this site is a finding of liability.

Section 04h

sayem314 / hooman

A public GitHub repository named hooman was created on 3 May 2020. Its one-line description is an HTTP interceptor to hoomanize Cloudflare requests. A later DuckDuckGo search for HAA Enterprises returned his personal listing immediately above that repository. Developers do say humanize. That coincidence is not hidden. The issue on this page is the adjacency — personal information, then what the package is published to do — read next to the AT&T witness file.

1 · On the record

The name, the listing, the published purpose

Three facts that do not need each other to be true, and that become an anomaly when they sit on one table. The AT&T employee’s writings about a sister, an iCloud, and account material on a phone are the context for later cell-phone claims. They live in their own window. This page does not retry that store. It points there.

Documented · 3 May 2020

A public interceptor named hooman

github.com/sayem314/hooman. Created 3 May 2020 — that is GitHub’s date, not a 2018 date from an investigator PDF. Description: http interceptor to hoomanize cloudflare requests. MIT. npm package hooman. “Hooman” is also a playful spelling of humanize. The package is named hoomanize. Both stay.

sayem314/hooman on GitHub

Documented · what it is published to do

Interceptor. Captcha. Cloudflare.

The About still prints topic tags: interceptor, captcha, recaptcha, cloudflare, cloudflare-bypass, scraper. That is the published purpose, not a tutorial. Install commands and captcha how-to from the harvest stay off this page.

Documented · the search still

Personal listing, then this repo

6 March 2025. Query HAA- Enterprises. First result: his name, San Diego, 2500 6th Ave — the Park Laurel building. Second: this GitHub, with that one-liner. He has since moved. The building line is why the still matters. The HAA folder on Figley’s office computer is recall, not in this file. The search still is.

Park Laurel — the building file

Context · the AT&T window

What the witness says a sister was receiving

Saqvan Ali wrote in 2020 that Hooman’s sister asked Del Mar AT&T to delete an iCloud; they refused. In 2026 he swore she had passwords, messages, photographs, and iCloud-related information on her phone and did not want him to see. That is alleged as to access. It is documented as a witness writing. Put it next to a public interceptor that sat beside his own listing. The reader can hold the anomaly. This page does not write the leap.

The AT&T statement — sister in the store

2 · Published purpose

Not a how-to. The About line.

Install commands and captcha-solving steps are not on this page.

3 · He wrote to the author

Remember me?

A Telegram still. Year not printed. Sayem dates a prior contact to early 2023, medical and government issues. Hooman then describes, under his name, a family fraud and a hacking program. That writing is documented. The program is alleged. The AT&T file remains the context for phone-side claims — not this chat, and not a use finding against the repository.

4 · The originals

Click a face. The context travels with it.

DocumentedCreated 3 May 2020
GitHub sayem314/hooman — public interceptor named hoomanize

Mobile GitHub still plus a desktop About still. Public repository. This page does not reprint install commands or captcha how-to.

github.com/sayem314/hooman, Public. One-line description: http interceptor to hoomanize cloudflare requests. npmjs.com/package/hooman. MIT license. Desktop About repeats that one-liner and prints topic tags including interceptor, captcha, cloudflare, cloudflare-bypass, scraper. Created date on GitHub: 3 May 2020. Not 12 January 2018.

Establishes. A public repository named hooman exists, created 3 May 2020, whose published description is an HTTP interceptor to hoomanize Cloudflare requests. The name and the published purpose are on the face. “Hooman” can also be a playful spelling of humanize. That coincidence is not hidden here.

Does not establish. Does not prove anyone used this package against him, opened an account, or installed it from a folder on an office computer. An HAA Enterprises folder on Figley’s computer is recall, not in this warehouse. This page does not reprint usage, keys, or a method. Investigator PDFs in the harvest that date the repo to 2018 are wrong; GitHub’s created date is 3 May 2020.

Source: GitHub harvest: Sayem314_Hooman Image.jpeg and interceptor to hoomanize cloudflare requests.png. Live repository created 3 May 2020.

Documented6 Mar 2025
HAA Enterprises search — his listing sits next to this repository

Same public raster as the Park Laurel HAA still. DOB and usage language on the face. iOS find bar stays — it is on the original.

DuckDuckGo query HAA- Enterprises. First result: Hooman A. Asbaghi, San Diego, primary residence 2500 6th Ave. Second result: github.com/sayem314/hooman — “http interceptor to hoomanize cloudflare requests.” That adjacency is the exhibit.

Establishes. A saved search for that name returned his personal listing immediately above this public repository. Personal information and what the package is published to do sit on one still. That is the anomaly. The building address is the point of the listing, not a current locator.

Does not establish. Does not prove the search followed a folder on Ryan Figley’s office computer — that folder is recall. Does not prove the package was run. Usage language under the GitHub title is on the face. Methods stay off this page.

Source: Park Laurel harvest: DuckDuckGO search of HAA Enterprises.jpeg. Same still as E-PL-HAA-DDG. This room is the GitHub file; Park Laurel is the building file. One still, two windows, not two copies of the folder story.

DocumentedMay 24 · year not on the face
Hooman to Sayem — “Remember me?”

Telegram still. Display name 74Y3M. Date chip May 24. Year is not printed.

Hooman: “Hi Sayem. Its Hooman. Remember me?” 74Y3M: “Yes I do” / “You contacted me early 2023” / “About medical and govt issues.” Hooman, quoting that line: he writes that he was defrauded by family members and that, to prevent discovery, they started a hacking program that would prevent his private internet access; he says he found out the details; “clever and SciFi-ish endeavor.”

Establishes. He wrote to the public author of sayem314/hooman. Sayem dates a prior contact to early 2023, about medical and government issues. The later message under Hooman’s name exists. That writing is the exhibit.

Does not establish. A message describing a hacking program is his account, not a finding the GitHub package was that program, not a finding Sayem ran it, and not a finding the family installed it. Year of this still is not on the face. This page does not teach a method.

Facts

No public URL mounted yet. The face is quoted above.

Source: GitHub harvest: HAtoSayemRememberme.jpeg.

ContextPublic name-frequency stills in the harvest
The given name Hooman is uncommon in the U.S.

Two public-web stills. Frequency estimates, not a census extract.

The name Hooman is uncommon in the U.S., appearing first in 1977, peak rank #1093 that year, Persian origin. Companion still: MyNameStats.com estimate, about 492 people in the U.S. with the first name Hooman, ranked 13,936th, prevalence about 0.150 per 100,000.

Establishes. Public name-frequency pages treat Hooman as an uncommon U.S. given name. That is context for why a package named hooman, sitting next to his own listing, is an anomaly worth putting on the same table as “humanize.” It is not a finding about intent.

Does not establish. Does not prove the repository was named for him. “Hooman” remains a real playful spelling of humanize. Both readings stay. Estimates vary by source.

Facts

No public URL mounted yet. The face is quoted above.

Source: GitHub harvest: The name Hooman is uncommon in the U.S.,.png and Hooman´s name is its prevalence is about 0.150 per 100,000 people..png.