Skip to main content

ClamAV history

The history of ClamAV

ClamAV began as an open-source scanner for Unix mail gateways in 2002. Its command-line tools, scanning library and signed definition updates later made it useful far beyond email.

ClamAV is an engine and toolkit

ClamAV is not a traditional all-in-one endpoint security suite. It provides a scanning engine, command-line tools, a daemon and definition updater that products and administrators can integrate into a wider security workflow.

ClamAV begins with email scanning

Tomasz Kojm released ClamAV 0.10 on 8 May 2002. The early project addressed a practical Unix problem: scanning email for malicious attachments and reducing unwanted content at the gateway before it reached users. The project was released under the GNU General Public License, which allowed administrators and developers to inspect, use and extend it.

The official ClamAV retrospective, Celebrating 20 years of ClamAV, explains that the project initially combined virus detection with spam-related email filtering. The malware-scanning capability became its enduring focus.

A toolkit takes shape

ClamAV developed into several cooperating parts. clamscan provided on-demand command-line scanning. clamd kept the engine and databases loaded for repeated requests. freshclam downloaded signed malware-definition updates. libclamav allowed other software to embed the scanning engine.

This separation helped ClamAV fit into mail gateways, file-upload pipelines, web services, storage appliances and incident-response tooling. Developers could call the scanning library or communicate with the daemon instead of building a malware engine from scratch.

From Sourcefire to Cisco Talos

Sourcefire acquired the ClamAV project in 2007 while keeping it open source. Cisco then acquired Sourcefire in 2013. ClamAV is now maintained within Cisco Talos, whose malware research and signature work support the engine and its official databases.

That history matters because ClamAV remains both an open-source project and a maintained security component. Its value depends on current engine releases, trusted definition updates and careful integration—not merely the presence of an old clamscanbinary.

What ClamAV can inspect

ClamAV grew beyond simple executable-file signatures. Its engine can examine archives, mail formats, documents, portable executable files and other structured content. The official file-type referencelists formats the engine recognises, while the libclamav documentation explains how applications can integrate scanning.

ClamAV today

The official ClamAV introductiondescribes a toolkit especially suited to email gateways, with a daemon, command-line scanner and automatic database updater. Linux can also use an on-access component, but the project does not present itself as a complete replacement for every endpoint protection function.

ClamAV is still widely useful wherever organisations need a local, automatable engine for known-malware detection. Its open interfaces make it particularly suitable for servers, gateways and appliances. Its limits make clear reporting equally important: skipped, unreadable or unvisited files must never be reported as clean.

Why Chowder uses ClamAV

Chowder adds a consistent graphical workflow around the engine: scanner and definition health, Quick, Full and Custom modes, progress, cancellation, history and explicitly controlled remediation. The engine remains ClamAV; Chowder makes its local use clearer on supported Linux x64 and Synology NAS systems.

Continue with practical ClamAV use cases, explore the history of computer viruses, or compare Chowder on Linux and Synology DSM.