# Detect data leaks

**URL:** <https://community.hubspot.com/t/detect-data-leaks/146870>\
**Category:** Study Group: Inbound\
**Created:** [March 3, 2026, 8:15am UTC](https://community.hubspot.com/t/detect-data-leaks/146870 "2026-03-03T08:15:34Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas5](https://avatars.discourse-cdn.com/v4/letter/t/f4b2a3/32.png) [@Thomas5](https://community.hubspot.com/u/Thomas5)\
**Post date:** [March 3, 2026, 8:15am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/1 "2026-03-03T08:15:34Z")

</div>

Quick question for fellow admins and security-minded folks:

Has anyone used (or built) a tool to automatically create decoy/fake Contacts in Hubspot to help detect and catch potential contact stealers?

I’m exploring the idea of seeding our org with realistic-looking dummy Contacts (with tracking fields, unique email domains, etc.) so that if they’re exported, emailed, or synced externally, we can flag suspicious activity.

Ideally, I’m looking for something that:  
- Can generate believable test data at scale  
- Allows tagging/flagging as honeytoken records  
- Helps monitor exports, reports, or API access tied to those records

If you’ve implemented something similar (custom build or external tool), I’d love to hear what worked, what didn’t, and any gotchas to watch for.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 3, 2026, 8:17am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/2 "2026-03-03T08:17:13Z")

</div>

Hi @Thomas5,

I’m not following the use case entirely - how would a contact get “stolen” and how would you find out about it, if you created decoy/fake contacts?

Best regards

---

<div class="post-metadata">

**Author:** ![Thomas5](https://avatars.discourse-cdn.com/v4/letter/t/f4b2a3/32.png) [@Thomas5](https://community.hubspot.com/u/Thomas5)\
**Post date:** [March 3, 2026, 8:23am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/3 "2026-03-03T08:23:46Z")

</div>

If you create a gmail account that you own, you will detect external emails from companies that are not supposed to know it. My concern is that I cannot create such email accounts at scale. I would need maybe 8-10 fake contacts. Does it make sense?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 3, 2026, 8:25am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/4 "2026-03-03T08:25:35Z")

</div>

@Thomas5 by leaked do you mean that someone gets hold of the email address itself to send spam to it? If so, how would you know through which source they did? It wouldn’t have to be necessarily HubSpot, it could be someone guessing it correctly.

---

<div class="post-metadata">

**Author:** ![Thomas5](https://avatars.discourse-cdn.com/v4/letter/t/f4b2a3/32.png) [@Thomas5](https://community.hubspot.com/u/Thomas5)\
**Post date:** [March 11, 2026, 6:53am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/5 "2026-03-11T06:53:18Z")

</div>

Hi Karsten,

For the sake of going a bit further in the discussion, check CRM Honeypots.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 3, 2026, 8:43am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/6 "2026-03-03T08:43:11Z")

</div>

@Thomas5 well…

- It could’ve been correctly guessed by a tool that iterates through common names and email syntax patterns.
- It could’ve been an “over the shoulder” attack on someone not protecting their screen.
- It could be any integration in HubSpot with contact view access, including app tokens and personal access tokens. There are many providers, generally seen as reputable, which offer integrations and have had issues along those lines, just thing LinkedIn or Canva.
- If users connect their calendar and inbox to HubSpot, it could be any app / extension that is installed on their computers.
- It could be someone with export permissions, moving around or even sharing a flat file with other people at your company or even outside of your company.

I’m not saying that information about a leak wouldn’t be helpful -- but you’re chasing symptomps where user training regarding the above topics is likely energy and budget better spent.

In any case, a tool flagging a leak wouldn’t be proof that HubSpot was hacked. It would be an indicator that your entire IT ecosystem would have to be reviewed.

---

<div class="post-metadata">

**Author:** ![Thomas5](https://avatars.discourse-cdn.com/v4/letter/t/f4b2a3/32.png) [@Thomas5](https://community.hubspot.com/u/Thomas5)\
**Post date:** [March 3, 2026, 8:47am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/7 "2026-03-03T08:47:41Z")

</div>

I see what you mean but one of my objectives is to check if former employees leave with our CRM data and if yes, how they re use it.

Thanks for the discussion

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 3, 2026, 8:57am UTC](https://community.hubspot.com/t/detect-data-leaks/146870/8 "2026-03-03T08:57:27Z")

</div>

@Thomas5 that might be an expensive way to find out about that. Generally, most user groups in HubSpot shouldn’t have export permissions. That in itself is a high security risk and should be limited to admins.

If exporting permissions are set up, then a user would be forced to copy information of individual contacts - in which case they likely step around decoy contacts as they’ll be able to tell apart valuable from non-valuable contacts.
