--- title: "#obfuscation articles | Hashnode" description: "Explore 111 articles tagged #obfuscation on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/obfuscation" --- Tag # #obfuscation 111 posts · 1 followers [VEILVM](https://hashnode.com/@veilvm) · [21h ago](https://hashnode.com/posts/string-encryption-is-not-enough-attackers-dump-your-javascript-at-runtime/6af7b8829ccc8cab3884cf54) ### [String encryption is not enough: attackers dump your JavaScript at runtime](https://veilvm.hashnode.dev/string-encryption-is-not-enough-attackers-dump-your-javascript-at-runtime?utm_source=hashnode&utm_medium=feed) String encryption hides literals in the file, not at runtime. This article explains how a runtime dump undoes string tables, why control-flow and VM protection raise the cost of finding when those strings are used, and why secrets still do not belong in client JavaScript. 7 min read · [veilvm.hashnode.dev](https://veilvm.hashnode.dev/string-encryption-is-not-enough-attackers-dump-your-javascript-at-runtime?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [23h ago](https://hashnode.com/posts/obfuscating-a-masstransit-app-without-breaking-message-routing/6af7995a4d4f1dd0e251dfb6) ### [Obfuscating a MassTransit App Without Breaking Message Routing](https://delta1labs.hashnode.dev/obfuscating-a-masstransit-app-without-breaking-message-routing?utm_source=hashnode&utm_medium=feed) A MassTransit application is a tempting obfuscation target: consumers, sagas and routing-slip activities are where your business logic lives, and most of it can be renamed, string-encrypted and virtua 14 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-masstransit-app-without-breaking-message-routing?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-dapper-data-access-layer-without-breaking-column-to-property-mapping/6af76eac3c4ecabfae838103) ### [Obfuscating a Dapper data-access layer without breaking column-to-property mapping](https://delta1labs.hashnode.dev/obfuscating-a-dapper-data-access-layer-without-breaking-column-to-property-mapping?utm_source=hashnode&utm_medium=feed) A micro-ORM like Dapper earns its speed by doing very little magic, but the one piece of magic it does keep is the piece that collides with obfuscation. When you write connection.Query("SELE 12 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-dapper-data-access-layer-without-breaking-column-to-property-mapping?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-hangfire-app-without-breaking-persisted-background-jobs/6af744b2edaa2d2ee5787348) ### [Obfuscating a Hangfire App Without Breaking Persisted Background Jobs](https://delta1labs.hashnode.dev/obfuscating-a-hangfire-app-without-breaking-persisted-background-jobs?utm_source=hashnode&utm_medium=feed) A Hangfire application looks like an easy obfuscation target. The job classes are plumbing; the valuable code is what they call into. But Hangfire has one seam that a naive obfuscation pass walks stra 12 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-hangfire-app-without-breaking-persisted-background-jobs?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding/6af71c549e0edbe117b6efc0) ### [Obfuscating strongly-typed configuration without breaking IOptions binding](https://delta1labs.hashnode.dev/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding?utm_source=hashnode&utm_medium=feed) A strongly-typed options class looks like the most ordinary C# in your solution — a POCO with public properties and nothing clever about it. But the moment you pass it to services.Configure, a few 10 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-net-aws-lambda-function-without-breaking-the-handler-string/6af6f02344c2a13c76df2a90) ### [Obfuscating a .NET AWS Lambda Function Without Breaking the Handler String](https://delta1labs.hashnode.dev/obfuscating-a-net-aws-lambda-function-without-breaking-the-handler-string?utm_source=hashnode&utm_medium=feed) A .NET AWS Lambda function is close to the ideal obfuscation target. It is a small class library — no Main in the managed case, no UI, one method that Lambda calls — that ships to infrastructure you d 12 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-net-aws-lambda-function-without-breaking-the-handler-string?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-signalr-app-without-breaking-the-hub-method-names-clients-call-by-string/6af6c5e57a2b303ee066ba68) ### [Obfuscating a SignalR app without breaking the hub method names clients call by string](https://delta1labs.hashnode.dev/obfuscating-a-signalr-app-without-breaking-the-hub-method-names-clients-call-by-string?utm_source=hashnode&utm_medium=feed) A SignalR assembly looks like ordinary C#, but a handful of its names are not really C# names at all — they are strings on a wire, and the obfuscator has to treat them as the opposite of everything ar 9 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-signalr-app-without-breaking-the-hub-method-names-clients-call-by-string?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-an-azure-functions-isolated-worker-app-without-breaking-function-discovery/6af695a9c457e93ca68c67d7) ### [Obfuscating an Azure Functions Isolated-Worker App Without Breaking Function Discovery](https://delta1labs.hashnode.dev/obfuscating-an-azure-functions-isolated-worker-app-without-breaking-function-discovery?utm_source=hashnode&utm_medium=feed) An Azure Functions app written on the .NET isolated worker model looks like the easiest thing in the world to obfuscate. It is a class library — no Main, no UI, a handful of methods decorated with \[Fu 11 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-an-azure-functions-isolated-worker-app-without-breaking-function-discovery?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [2d ago](https://hashnode.com/posts/obfuscating-a-localized-net-app-keeping-istringlocalizer-resx-and-satellite-assemblies-working-under/6af59f971aa18b8838553e49) ### [Obfuscating a localized .NET app: keeping IStringLocalizer, .resx and satellite assemblies working under renaming](https://delta1labs.hashnode.dev/obfuscating-a-localized-net-app-keeping-istringlocalizer-resx-and-satellite-assemblies-working-under?utm_source=hashnode&utm_medium=feed) Localization is a by-name subsystem, and by-name is the one word that should make anyone reach for an obfuscator carefully. Every translated string your app shows was resolved at runtime by matching a 8 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-localized-net-app-keeping-istringlocalizer-resx-and-satellite-assemblies-working-under?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [2d ago](https://hashnode.com/posts/obfuscating-a-winui-3-app-what-xbind-already-made-rename-safe-and-the-three-strings-that-still-break/6af57b158f470ae4c63447bd) ### [Obfuscating a WinUI 3 app: what {x:Bind} already made rename-safe, and the three strings that still break it](https://delta1labs.hashnode.dev/obfuscating-a-winui-3-app-what-xbind-already-made-rename-safe-and-the-three-strings-that-still-break?utm_source=hashnode&utm_medium=feed) A WPF obfuscation guide does not transfer to WinUI 3, and a UWP one only half-transfers, because the thing that decides what survives a rename is the XAML compiler, and WinUI 3's is closer to Avalonia 10 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-winui-3-app-what-xbind-already-made-rename-safe-and-the-three-strings-that-still-break?utm_source=hashnode&utm_medium=feed)