Development of Spam Protection Module for 1C-Bitrix

Introduction

The feedback form starts receiving 200–300 spam submissions per day. Managers stop trusting form data and begin to miss real leads. The site loses conversion, and processing junk takes hours of work—a reality in e-commerce. Bitrix offers built-in Google reCAPTCHA v2 through the form component, but bots have long learned to bypass it using captcha-solving services. High-load forms require multilayered protection. We have been developing modules for Bitrix for over 5 years and have implemented more than 50 spam protection projects, so we know which method combinations are effective under different loads. Contact us for a free audit of your current protection—we'll identify weak spots and select a configuration.

Why a Single Method Doesn't Work

Each spam protection method has weaknesses:

Effective protection is multilayered, where each method covers the weaknesses of others. A module built on honeypot + rate limit is about 10 times more effective in terms of price/quality than a single captcha. According to a Spamhaus report, more than 85% of spam is generated by bots.

Module Architecture

Layer 1 — Honeypot + Timer

A hidden field named website (bots will like it) and a field form_fill_time. If website is filled or form_fill_time < 3 seconds, the submission is likely from a bot with 99% probability.

Layer 2 — Behavioral Analysis

JavaScript writes mouse events and keystrokes into a hidden field. On submission, the server checks: was there real mouse movement, was there reasonable typing speed? Bots mimicking humans spend resources on this and rarely use it for mass attacks.

Layer 3 — Rate Limiting by IP and Fingerprint

No more than N submissions from one IP in M minutes. Fingerprint is built from User-Agent, Accept-Language, Accept-Encoding — not from IP. Rules are stored in myvendor_spam_rate:

CREATE TABLE myvendor_spam_rate (
    fingerprint VARCHAR(64) NOT NULL,
    form_id     VARCHAR(100),
    hits        INT DEFAULT 1,
    first_hit   TIMESTAMP DEFAULT NOW(),
    last_hit    TIMESTAMP DEFAULT NOW(),
    blocked     BOOLEAN DEFAULT false,
    PRIMARY KEY (fingerprint, form_id)
);

Layer 4 — Reputation Databases

Check sender IP via AbuseIPDB API or Spamhaus. If score is above threshold, block or increase verification difficulty. Results are cached in myvendor_spam_ip_cache with a TTL of 24 hours to avoid hitting the external API on every request.

Layer 5 — ML Text Classifier

For forms with text fields (message, comment) — content analysis. A simple naive Bayes classifier trained on historical spam/non-spam data of the specific site. Stored in myvendor_spam_model, retrained by an agent once a week.

More about honeypot can be read on Wikipedia, and about reputation databases in AbuseIPDB documentation.

Integrating with Bitrix Forms

Intercept forms via the OnWebFormResult_Add event (module form):

AddEventHandler('form', 'OnWebFormResult_Add', function(&$arFields, &$arValues) {
    $verdict = \MyVendor\Spam\Analyzer::analyze(
        ip: $_SERVER['REMOTE_ADDR'],
        fingerprint: \MyVendor\Spam\Fingerprint::get(),
        formId: $arFields['FORM_ID'],
        fields: $arValues,
        fillTime: (int)($_POST['form_fill_time'] ?? 0)
    );

    if ($verdict->isSpam()) {
        $arFields['COMMENTS'] .= "\n[SPAM: {$verdict->getReason()}]";
        $arFields['STATUS'] = 'N';
    }
});

Important: spam submissions are not deleted but marked. This allows periodic review of marked submissions and correction of false positives—data for improving the classifier.

Protecting Registration and Cart

Spam bots attack not only contact forms but also the registration form (creating junk accounts) and the cart (testing stolen cards through small payments). The module extends to these points: for registration—same honeypot + rate limit; for cart—detecting patterns (many small orders from different cards in a short time).

How We Test the Module

Before launch, we run the module on your site's historical data (if spam logs exist) or on synthetic traffic simulating bots. We measure the percentage of false positives and missed spam submissions. We adjust thresholds to minimize both metrics. After deployment, the module continues to learn from new data.

Development Process

1. Threat analysis: study types of spam attacks on your project.
2. Architecture design: choose a combination of layers based on load.
3. Implementation: write module code considering your forms.
4. Testing: verify on historical data and synthetic data.
5. Deployment and monitoring: install on the production server, track metrics.

What's Included in the Work

• Technical specification with method selection for your load.
• Development and configuration of the module for specific forms (feedback, registration, cart).
• Configuration and support documentation.
• Administrator training (1–2 hours online).
• Free support for 1 month after launch.

Development Timelines

Before ordering a complex solution, assess the scale of the problem: sometimes honeypot + rate limit is enough, and it will solve 95% of spam in 1 week. For an accurate assessment of your project, contact us—we will analyze your current situation for free and offer an optimal configuration. Get a consultation today.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.