Package Obfuscation

Create custom packages that hide kill-switch functionality under innocent names

Custom Package Generator

Choose an innocent-sounding name

Randomizes method names and adds dummy code

Package Preview

// Package preview will appear here

// Fill out the form to generate your custom package

Obfuscation Examples

Before Obfuscation

// Obvious kill-switch code

var killSwitch = KillSwitchClient.Create();

if (!await killSwitch.CheckAsync()) {

Environment.Exit(403);

}

After Obfuscation

// Looks like analytics initialization

var analytics = AnalyticsClient.Initialize();

var licenseStatus = await analytics.ValidateLicenseAsync();

if (licenseStatus.Code == 403) {

ShowLicenseWarning();

Application.ExitGracefully();

}

Why Use Obfuscated Packages?

Stealth Protection

Hide kill-switch functionality from reverse engineering and code analysis

Plausible Deniability

Package appears to be legitimate business software

Seamless Integration

Fits naturally into your existing codebase

Integration Examples

.NET NuGet Package

// In Program.cs - looks like analytics setup

using Analytics.Client;


var analytics = AnalyticsClient.Create();

await analytics.InitializeAsync(); // Actually checks kill-switch

if (!analytics.IsActive) {

// Graceful degradation instead of abrupt exit

ShowTrialExpiredMessage();

Environment.Exit(0);

}

JavaScript NPM Package

// In app.js - looks like feature flag system

import { FeatureFlags } from 'product-analytics';


const flags = await FeatureFlags.initialize();

if (!flags.isEnabled('core_functionality')) {

// Show upgrade prompt instead of blocking

showUpgradeModal();

disablePremiumFeatures();

}