# \[…Duplicate thread\]

**URL:** <https://community.smartthings.com/t/duplicate-thread/163488>\
**Category:** Apps & Clients\
**Created:** [May 12, 2019, 4:34am UTC](https://community.smartthings.com/t/duplicate-thread/163488 "2019-05-12T04:34:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JDRoberts](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/jdroberts/32/56577_2.png) [@JDRoberts](https://community.smartthings.com/u/JDRoberts)\
**Post date:** [May 12, 2019, 4:40am UTC](https://community.smartthings.com/t/duplicate-thread/163488/2 "2019-05-12T04:40:17Z")

</div>

See the current active thread:

> [@SmartThings App source code and keys leaked (May 2019 article)](https://community.smartthings.com/t/smartthings-app-source-code-and-keys-leaked-may-2019-article/163204):
>
> TechCrunch released this article. Not sure if it has been posted before. [https://techcrunch.com/2019/05/08/samsung-source-code-leak/?utm\_source=feedburner&utm\_medium=feed&utm\_campaign=Feed%3A+Techcrunch+(TechCrunch)](https://techcrunch.com/2019/05/08/samsung-source-code-leak/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%28TechCrunch%29)

No Telling quite how risky it is yet. Samsung continues to say that the code exposed was only a test site. The person who reported the vulnerability appears to think there’s more to it than that. But no customer data was exposed, just the source and the developer keys to that code.

Given the absence of any announcements from Samsung, it would appear to be no real risk to customers, although it does make the third-party developers who were working for Samsung look pretty sloppy with regards to security.

---

_[View the full topic](https://community.smartthings.com/t/duplicate-thread/163488)._