# \[BUG REPORT\] - uasset files not secured when packaged

**URL:** <https://forums.unrealengine.com/t/bug-report-uasset-files-not-secured-when-packaged/416929>\
**Category:** Platform & Builds\
**Tags:** security, unreal-engine, bug-report, packaging-projects, question\
**Created:** [February 10, 2018, 9:37am UTC](https://forums.unrealengine.com/t/bug-report-uasset-files-not-secured-when-packaged/416929 "2018-02-10T09:37:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TorQueMoD](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/torquemod/32/710746_2.png) [@TorQueMoD](https://forums.unrealengine.com/u/TorQueMoD)\
**Post date:** [February 10, 2018, 9:37am UTC](https://forums.unrealengine.com/t/bug-report-uasset-files-not-secured-when-packaged/416929/1 "2018-02-10T09:37:12Z")

</div>

So I just had a friend try out my game that released on Steam back in June 2017 and he’s discovered that he can access any of the files in the game and extract them which then gave him the ability to add any info he wanted to the online score board. I’ve already reached out to Epic Leaderboards about this security issue, but it’s also a risk on your end because if he wasn’t able to access the files to begin with then he wouldn’t have been able to do anything.

I was under the impression that once the files were packaged they were encrypted and inaccessible but this is obviously not the case. It’s rather disconcerting really.

---

<div class="post-metadata">

**Author:** ![SupDeity](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SupDeity](https://forums.unrealengine.com/u/SupDeity)\
**Post date:** [April 22, 2018, 9:08am UTC](https://forums.unrealengine.com/t/bug-report-uasset-files-not-secured-when-packaged/416929/2 "2018-04-22T09:08:14Z")

</div>

you need to encrypt them i think, go to ur project settings and search encrypt and create a encryption key and then just check the stuff u want to encrypt [there are checkboxes]

---

<div class="post-metadata">

**Author:** ![trdwll](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@trdwll](https://forums.unrealengine.com/u/trdwll)\
**Post date:** [May 2, 2018, 3:02am UTC](https://forums.unrealengine.com/t/bug-report-uasset-files-not-secured-when-packaged/416929/3 "2018-05-02T03:02:21Z")

</div>

As Jurrasic Studios said above, you need to encrypt your files via in the Engine. 4.19 added pak file signing and encryption. See [Unreal Engine 4.19 Released! - Unreal Engine](https://www.unrealengine.com/en-US/blog/unreal-engine-4-19-released) for more information. (search for encryption)

_These features can now be controlled in **Project Settings** , under the **Project** section, in the **Crypto** panel._

[https://dnnrz1gqa.blob.core.windows.net/portals/Images/Support/Builds/ReleaseNotes/4\_19/image\_34.png?sr=b&si=DNNFileManagerPolicy&sig=ajg1t85%2FW%2F%2FhSwN%2BtNZQ55szR5vobHgEHHD5omayuq0%3D](https://dnnrz1gqa.blob.core.windows.net/portals/Images/Support/Builds/ReleaseNotes/4_19/image_34.png?sr=b&si=DNNFileManagerPolicy&sig=ajg1t85%2FW%2F%2FhSwN%2BtNZQ55szR5vobHgEHHD5omayuq0%3D)
