LogoLogo
  • Welcome to Cyphor
  • .NET Code Obfuscation
    • Getting Started
    • How to Obfuscate
    • Basic Code Obfuscation
      • Symbol Renaming
      • Body Mutation
      • Control Flow
      • Constant Encryption
      • Call Hiding
      • Debug Protection
      • Integrity Checks
      • Self Healing
    • Advanced Obfuscation
      • Attribute-Based Obfuscation
      • Guide to obfuscation
      • Code Inlining
      • What is RASP?
      • Protections that protect each other
      • Program not working after obfuscation
      • Keeping performance with obfuscation
      • Virtualization
  • Dashboard
    • Files
    • Billing
      • Pay as you go
      • Examples
    • Projects
      • Code Guard Tasks
      • Permissions
        • Roles
      • Files
      • SAML and SSO
  • Code Guard
    • Introduction
    • Implement with your licensing system
      • Setting up a gateway
      • Setting up the SDK
    • Secured values
      • Dynamic values
      • Code Encryption
        • Page 1
    • Preventing analysis
    • Enhanced visibility
      • Disabling tracing on production
      • Logging external methods
      • Optimizing Memory Usage
    • Edge connectivity
    • Preventing modifications
      • Preventing assembly load
      • Allowing partial tampering
      • Enterprise EDRs and XDRs
      • Dynamic Hook protection
      • Thread hijacking
      • Guard Checksums
      • DLL Injection
      • Handling complex RE attacks
        • Custom payload detection
    • Granular Integrity Checks
    • Virtualized Environments
    • Troubleshooting
    • Threat database
    • Real time alerts
      • Alert Insights
  • CLI Tool
    • Introduction
    • Global options
    • Profiles
    • Projects
    • Obfuscator
      • Obfuscation Schemes
      • Task templates
      • Protecting files
        • Global obfuscation flags
        • Using templates to obfuscate files
        • Quick obfuscation
      • Monitoring obfuscation jobs
    • Securing local storage
Powered by GitBook
On this page
  • What is DLL injection?
  • Potential drawbacks of preventing DLL injection
  • Toggling DLL detection on and off in the dashboard

Was this helpful?

  1. Code Guard
  2. Preventing modifications

DLL Injection

PreviousGuard ChecksumsNextHandling complex RE attacks

Last updated 1 year ago

Was this helpful?

What is DLL injection?

DLL injection is a technique used by malicious actors to execute arbitrary code on a target computer by injecting a dynamic-link library (DLL) into a running process.

This allows the attacker to modify and tamper the process behavior without modifying the original assembly, potentially bypassing any existing integrity checks.

Potential drawbacks of preventing DLL injection

In some instances, attempting to identify DLL injection can lead to false attack signals. This typically occurs when legitimate DLLs are injected into memory by authorized programs, such as antiviruses or applications that interact with your process.

The presence of a third party DLL in memory is not a definitive sign of a tampering attempt, nevertheless, it's important to investigate each alert to mitigate the risk of a potential attack spreading further.

When creating DLL injection reports, Codeguard offers valuable insights into the injected code.

Please refer to our to learn more.

Toggling DLL detection on and off in the dashboard

Customers have the option to toggle DLL detection on and off in the dashboard. This can be useful in situations where DLL injection is used for legitimate purposes, such as software development or testing.

To toggle DLL detection on and off in the dashboard, follow these steps:

  1. Log in to the dashboard and navigate to the settings page.

  2. Locate the "DLL detection" section and click on the toggle switch to enable or disable DLL detection.

  3. Save your changes and the new setting will take effect immediately.

Please note that disabling DLL detection may increase the risk of unauthorized access to your system and the sensitive information it contains. It should only be done in situations where DLL injection is needed for legitimate purposes and appropriate security measures are in place.

compatibility page