Suspicious.
The post itself reads as a polished success story, but the comment section shows a single account (u/Big_Employment1624) posing as multiple distinct users asking questions and then promoting exposd.dev—a domain only 18 days old. This pattern, combined with u/hugin_studio's detection of the same operator across comments and the defensive counter-narrative in later replies, indicates coordinated self-promotion and vote/comment manipulation rather than organic discussion.
Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 7 comments and 2 unique commenter accounts.
- Signal count: 1 high, 1 medium, 0 low flags; 0 coordination-class signals.
The registry's RDAP record shows exposd.dev was registered on 2026-06-10. A marketing push running on a domain this young is the classic launch-and-burn pattern — by the time complaints accumulate, the operator has rotated to a fresh domain.
Full evidence trailSources, public checklist, values lens, network map, account coverage, archive, and sharing tools.
Review before sharing.
Hugin reports are evidence packets, not accusations. Use the rating as a prompt to inspect sources, limitations, and archived material before quoting a claim elsewhere.
I quit my job to vibe code a LinkedIn Automation SaaS tool, with no Engineering background, and made ~$3.6k in the first 3 months
Source checks
10 public comments loaded for r/B2BSaaS.
Public comment bodies were retained with the report snapshot.
3 author age values were unavailable after Reddit profile JSON, old Reddit profile HTML, and archive fallbacks.
1 selected author history checked; 1 unavailable.
7 reply edges mapped.
0 same-hand writing pairs surfaced.
4 unique external identifiers extracted.
0 prior archive matches returned.
Show your work
Deterministic explanation of the stored scan inputs behind the verdict. This is not hidden model reasoning; it is the evidence checklist Hugin can show publicly.
Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 7 comments and 2 unique commenter accounts.
- Signal count: 1 high, 1 medium, 0 low flags; 0 coordination-class signals.
- The scan crossed the caution threshold, but did not show enough stacked proof for likely scam.
What pushed risk up
The registry's RDAP record shows exposd.dev was registered on 2026-06-10. A marketing push running on a domain this young is the classic launch-and-burn pattern — by the time complaints accumulate, the operator has rotated to a fresh domain.
- registered 2026-06-10
The registry's RDAP record shows hugin.studio was registered on 2026-05-21 — recent enough to note alongside the other signals, though not damning on its own.
- registered 2026-05-21
What limited confidence
3 scanned authors had unknown account age. Profile metadata remained unavailable for 3 hosted fetches after archive fallbacks. Absence of young-account signals is lower confidence.
What kept the rating lower
Hugin mapped 7 reply edges and did not find a mutual-reply clique.
The writing-style comparison ran and did not surface same-hand pairs.
- 3 author account ages were unavailable after profile metadata and archive fallbacks.
- 1 selected author history was unavailable to the scan.
- Username shape alone is never treated as a finding; it is only context when stronger public signals also appear.
- Likely scam: multiple high-severity signals, prior identifier reuse, or several coordination signals stacking together.
- Suspicious: one high-severity signal, multiple medium signals, or one concrete coordination signal that deserves review.
- Inconclusive: weak, conflicting, or partial signals where the scan cannot justify either trust or a stronger warning.
- Looks legitimate: no structural red flags, available metadata, and clean coordination passes.
Values lens
Use scans to slow down, inspect public signals, and keep uncertainty visible. Never use them to harass, shame, or flatten people into a verdict.
Fair-use checks
- What was observed, and what is interpretation?
- What data is missing, blocked, or confidence-limiting?
- Would the wording feel fair if it were about someone you care about?
What the post is doing
- u/Big_Employment1624 appears in comments 1, 2, 3, and 6—initially as a skeptical 'software engineer' asking about distribution, then as the actual exposd.dev founder, then deflecting the accusation
- exposd.dev domain is only 18 days old; hugin.studio (the accuser) is only 38 days old—both launched within a compressed timeframe consistent with a coordinated campaign
- All top comments have 0 score and read as a manufactured Q&A sequence designed to elicit promotional links rather than organic community discussion
- u/Big_Employment1624 promotes exposd.dev in comment 2 via direct link, immediately after posing as a third-party questioner in comment 1
- Defensive counter-narrative in comment 6 claims 'false positive' and 'real founder,' but does not deny operating multiple comment personas—only reframes it as legitimate feedback
Automated flags
The registry's RDAP record shows exposd.dev was registered on 2026-06-10. A marketing push running on a domain this young is the classic launch-and-burn pattern — by the time complaints accumulate, the operator has rotated to a fresh domain.
- registered 2026-06-10
The registry's RDAP record shows hugin.studio was registered on 2026-05-21 — recent enough to note alongside the other signals, though not damning on its own.
- registered 2026-05-21
Coordination map
Who replied to whom in the scanned comments. Organic threads branch out from the post; accounts that reply back and forth to each other (red links) or hub around one shared identifier (dashed amber) are the structural fingerprints of a coordinated pod.
- mutual-reply ring member
- account under 30 days
- other commenter
- replied to each other
- shared identifier
Commenter patterns
Recent public Reddit activity for the OP and selected accounts, plus same-hand writing checks when the stylometry pass runs. These are coverage-limited evidence summaries, not identity or availability claims.
Reddit blocked the recent-activity fetch from Hugin's scanner during this run. Treat this as missing coverage, not a finding about the account.
The writing-style pass ran and did not surface same-hand pairs.
Account age coverage
OP and scanned commenters are shown when Hugin recovered profile metadata or an oldest-public-activity age floor. Lower-bound ages are labeled as estimates; unknown age remains missing coverage, not a finding about the account.
Archived evidence
Snapshot of the post and comments at scan time. Preserved here so the evidence survives even if it gets deleted on Reddit.
- u/Big_Employment1624score 0Are these things really true? I have been a software engineer for 4 years, and I couldn't even get one paid user for my platform, and you are killing it. How did you crack your distribution channel and get your first customers?
- u/Downtown_Pudding9728score 0Yes completely true. Distribution is definitely the hardest part and something I still struggle with - less so acquiring customers, but getting people to stay with the tool long term and renew consistently. I have many day 1’s that I still communicate with regularly, but as I said, retention is the much harder skill than distribution. If you’re not getting new users, it might be worth evaluating whether there’s really enough demand for what it is. My distribution channel is social media, and dogfooding my actual tool. I use ZenMode to sell ZenMode, and it works. Hope that helps!
- u/Big_Employment1624score 0I'm still in the process of figuring out the demand. What I'm building is a frontend vulnerabiliy scanner tool where a person can monitor their website for leaks. I've got like 150 free rreports till now, but I'm not able to get people to join the waitlist for the paid tool. You cantray generating a report for your website. https://www.exposd.dev/
- u/Downtown_Pudding9728score 0This is free with trufflehog, sentry, and other repos that anyone can use. I’d suggest building something that solves a problem almost nothing else does.
- u/Big_Employment1624score 0You are right on solving a problem that I can solve better. I started it off as free tool but paid tool signals have been weak. Thanks for the feedback though
- u/hugin_studioscore 0For anyone trying to sanity-check this thread, I ran a public scan and saved the report here: https://hugin.studio/r/aa7-5hd-ex9 Short version: it came back likely scam (Sock-puppet ring, self-promotion funnel). The post is a suspiciously polished 'quit my job and built a SaaS' success story, but the same user ( u/Big_Employment1624 ) appears in all three top comments promoting a different product (exposd.dev, a vulnerability scanner) while pretending to be a separate person asking questions. This is a classic sock-puppet reply ring where the OP manufactures engagement and subtly cross-promotes another tool. The exposd.dev domain is only 18 days old, consistent with a rapid-cycle grift funnel. This pass looked at 1 commenters scanned. The clearest things it surfaced were Linked domain exposd.dev is only 18 days old. The report saves the public post/comments snapshot and shows the checks behind the label: account-age coverage, reply structure, repeated identifiers, and writing-style comparison when enough data is available. Important caveat: this is public-structure evidence, not proof of intent or identity. Missing account metadata lowers confidence, and username shape alone is never treated as evidence.
- u/Downtown_Pudding9728score 0Let me guess - you’re trying to sell the scan software you’re using? I have no connection to the big employment person (ask him yourself) so your scan is wrong anyway. I even told him what he’s building is available for free online, would be a weird/pointless conversation to have with myself.
- u/hugin_studioscore 0No ~ just a free utility
Original on Reddit: https://www.reddit.com/r/B2BSaaS/comments/1ugp47i/comment/ouejxkv/ — “I quit my job to vibe code a LinkedIn Automation SaaS tool, with no Engineering background, and made ~$3.6k in the first 3 months”
Share this report
Share this link in a Reddit reply when the thread needs supporting evidence. The report stays public so anyone reading the thread can review the data themselves.
Reports like this stay free for everyone. Keep Hugin free →