Fixing BAILOUT malware detected cPanel with Imunify360 When Using Adsterra Ads

If you’re on cPanel shared hosting and see the “BAILOUT malware detected” warning after inserting Adsterra ad code, you’re facing a common Imunify360 false positive issue. This guide explains the cause, whether you can fix it yourself, and the safest way to resolve it.

Why You See the “BAILOUT Malware Detected” Error

Imunify360 (or ImunifyAV) is a powerful security tool for cPanel servers that scans and blocks files matching known malware patterns.
Adsterra often delivers ads via obfuscated JavaScript — code that looks scrambled to prevent tampering.

While this is a normal ad delivery method, the obfuscation pattern can trigger Imunify’s malware signatures, leading to:

BAILOUT malware detected

This is usually a false positive, meaning the code is safe but misidentified as malicious.

Can You Fix It on Shared Hosting?

On shared hosting, you can’t directly edit Imunify360 whitelist rules or signature databases because these are managed by your hosting provider.
This means:

• You cannot whitelist files yourself
• All changes require provider approval

Possible Workarounds:

1. Save the Adsterra code in a separate .js file within a secure directory
2. Encode the code in Base64 and serve it dynamically
3. Apply a strict Content-Security-Policy (CSP) to allow scripts only from trusted domains

⚠ However, on shared hosting, even these may fail if Imunify scans before serving the file.

The Recommended Solution – Contact Support

Since this is a server-level restriction, the most effective method is to open a support ticket with your hosting provider.

When creating your ticket, include:

• The exact error (BAILOUT malware detected)
• The Adsterra code sample (if safe to share)
• The file path or URL where the code is used
• A request to whitelist the file or directory after verification

Conclusion

The “BAILOUT malware detected” issue in Imunify360 cPanel is almost always a false positive triggered by obfuscated Adsterra scripts.
On shared hosting, you cannot bypass this yourself.
Your best option is to contact your hosting provider and request them to whitelist the verified ad code or its storage path.

By providing clear details in your support ticket, you’ll help them resolve the issue quickly — keeping your ads running and your site secure.