Magento 2 Module – Security Scanner and Malicious Code Detection
Magento Modules: Clear Guidelines
You purchase the module once, with no domain restrictions
Free installation and updates via Composer
Affiliate Program
Technical support for Magento
Clear guidelines for licensing Magento modules
Magento Module Code Security
Kowal Security Scan is an advanced yet lightweight solution that provides an additional layer of security for your Magento 2 store without the need to install additional software such as YARA.
Main module features:
- File scanning – detects unauthorized changes, new files, and deleted files in the store directory.
- Malicious code detection – analyzes file contents for known attack techniques
- Database scanning – searches tables such as
cms_block,cms_page,core_config_data,email_template,product_descriptionfor suspicious content or code. - Security assessment of URLs in content using Google Safe Browsing
- Result reporting – results are saved to a log table with information about the time, type, and threat level (LOW, MEDIUM, HIGH).
- Email report delivery – only when threats are detected. The email address and reporting enablement can be configured from the Magento admin panel.
- Full automation – CRON tasks run cyclically, and each task can also be launched manually via CLI.
New: Google Safe Browsing API integration
Thanks to integration with the Google Safe Browsing API, the module can detect malicious links such as those leading to phishing, malware, or unwanted software contained in your store content: CMS blocks, product descriptions, transactional emails, and more.
Where does it look for threats?
The module analyzes the most important areas where malicious code may appear:
- CMS block content
- CMS pages
- System configuration (core_config_data)
- Email templates (Magento plus newsletter)
- Product descriptions
- Customer reviews
Notifications and logs
- Automated logging of suspicious entries to the module's dedicated log table
- Email report delivery with the option to specify the recipient and sender in the configuration
- Risk level indication for each entry (High, Medium, Low)
Example use cases:
- Detection of malicious code embedded by unauthorized users, such as iframe from .ru, .tk, and similar domains.
- Detection of attempts to overwrite files through file injection attacks.
Why choose it?
- No external dependencies – works immediately after installation.
- Security without affecting store performance.
- Also works on shared hosting – no root access required.
Compatibility:
- Magento Open Source 2.3.x – 2.4.x
- Magento Commerce (Adobe Commerce) – successfully tested
Package includes:
- Module with CRON and CLI tasks
- Database schema and log tables
- Configuration in the Magento admin panel
Documentation and support
We provide documentation for every module, along with the option to contact our technical support team.
Protect your Magento 2 store today with Kowal Security Scan!
Version: 1.0.27
31.03.2026
We have expanded the Kowal_SecurityScan module with new features related to threat analysis and report administration.
New features
- Added OpenAI integration for analyzing changed files and suspicious database records.
- Reports and email messages now include a risk assessment and recommended actions in the following areas:
- Magento
- server
- firewall
- Added OpenAI configuration in the Magento panel, including:
- enabling/disabling AI analysis
- API key
- model selection
- context limit passed for analysis
Improvements
- The OpenAI model list is now fetched dynamically from the API and presented in the configuration as a dropdown.
- Expanded email content with Magento store identification:
- store domain
- store URL
- The store domain is also added to the message subject, making it easier to manage multiple instances.
Automation and maintenance
- Added a new cron job that cleans old entries from the reports table.
- The report retention period is configurable from system.xml as a number of days.
Technical fixes
- Organized the logic for analyzing suspicious files and records.
- Improved handling of the data context passed to AI analysis.
- Removed a DI compilation issue related to the previous OpenAI client implementation.














