# Looking for security contact at MTCaptcha

**URL:** <https://community.disclose.io/t/looking-for-security-contact-at-mtcaptcha/398>\
**Category:** Hacker Connect\
**Created:** [February 10, 2022, 8:58am UTC](https://community.disclose.io/t/looking-for-security-contact-at-mtcaptcha/398 "2022-02-10T08:58:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![acut3](https://avatars.discourse-cdn.com/v4/letter/a/dbc845/32.png) [@acut3](https://community.disclose.io/u/acut3)\
**Post date:** [February 10, 2022, 8:58am UTC](https://community.disclose.io/t/looking-for-security-contact-at-mtcaptcha/398/1 "2022-02-10T08:58:35Z")

</div>

I’ve tried to contact MTCaptcha using their two documented email addresses (info@ and support@) but didn’t get any response. If you know someone there I’d appreciate an email address.

---

<div class="post-metadata">

**Author:** ![sickcodes](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.disclose.io/sickcodes/32/29_2.png) [@sickcodes](https://community.disclose.io/u/sickcodes)\
**Post date:** [February 19, 2022, 8:46pm UTC](https://community.disclose.io/t/looking-for-security-contact-at-mtcaptcha/398/2 "2022-02-19T20:46:27Z")

</div>

So the company has one (1) employee on LinkedIn, so if anyone has 1st or 2nd degree access to this LinkedIn account’s employee page: [https://www.linkedin.com/company/mtcaptcha/](https://www.linkedin.com/company/mtcaptcha/)

I left them a comment: [MTCaptcha on LinkedIn: 95 Top San Francisco Cyber Security Companies and Startups of 2021](https://www.linkedin.com/feed/update/urn:li:activity:6832702270313000960/)

If nothing happens and it’s not a CVE, it’s probably useless to report it publicly.

Since it’s used by ABB (ICS), I would FORWARD the email your sent already to

ABB and CC: [NCCICCUSTOMERSERVICE@hq.dhs.gov](mailto:NCCICCUSTOMERSERVICE@hq.dhs.gov)

I would consider it ICS, so just forward the first email you sent to ABB and CC ICS CERT (above).

Once you’ve done all that, and if nobody responds, wait a wait, then you can probably just think about going public.

---

<div class="post-metadata">

**Author:** ![acut3](https://avatars.discourse-cdn.com/v4/letter/a/dbc845/32.png) [@acut3](https://community.disclose.io/u/acut3)\
**Post date:** [February 19, 2022, 10:34pm UTC](https://community.disclose.io/t/looking-for-security-contact-at-mtcaptcha/398/3 "2022-02-19T22:34:31Z")

</div>

Thanks for looking into this!

I did see their LinkedIn and the article you mentioned, but didn’t think of leaving a comment there.

ABB doesn’t seem to be using them anymore. I did find a few companies using them on Shodan/Censys, but none of them appear to have disclosure policies except for the BBP where I orignaly reported the vulnerability.

---

<div class="post-metadata">

**Author:** ![sickcodes](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.disclose.io/sickcodes/32/29_2.png) [@sickcodes](https://community.disclose.io/u/sickcodes)\
**Post date:** [February 19, 2022, 10:43pm UTC](https://community.disclose.io/t/looking-for-security-contact-at-mtcaptcha/398/4 "2022-02-19T22:43:48Z")

</div>

Damn, you could try [registrar-abuse@google.com](mailto:registrar-abuse@google.com)

eiqv0p5dmcub@contactprivacy.email will go directly to the domain owner, via the WHOIS.

Abuse should work pretty quick though!
