Skip to content
Malnox
Features

Everything that runs on your machine, listed without hiding anything

Every feature below exists in version 1.1.31 and has tests. Where something is not ready — the kernel driver, for instance — we say so explicitly.

At a glance

file engines
16file engines
DLP policies
5DLP policies
YARA rules
67YARA rules
RBAC roles
3RBAC roles
canary interval
60 scanary interval
network requests
0network requests
Download for Windows
The engines

17 engines, four layers

Detection, content, context and processes complete each other. All 16 file engines are enabled by default; the memory scanner is started manually. Each can be disabled individually in configuration.

Detection

7

The engines that decide whether a file is dangerous: signatures, rules, binary structure and static heuristics.

01

Hash

Signatures

SHA-256 and MD5 against the local signature database.

The first and cheapest gate: if the hash is known, the verdict is instant without opening the file.

02

YARA (own engine)

Rules

Own parser and evaluator for YARA syntax, with needle prefiltering.

Supports text with nocase/wide/ascii/xor/fullword, hex with wildcards and jumps, regex, any/all/n of them conditions, offsets, filesize and uint16(0).

03

YARA-X

Rules

YARA-X over the bundled 10-file .yar package, with ndjson output.

Independent from the in-house implementation: if the two disagree, you see it in the report.

04

MalNOX Core Engine

Signatures

MalNOX signature engine with the signature database shipped in the package.

Runs locally, with no cloud updates in the detection path. Signatures update through signed packages.

05

PE analysis

Structure

PE/PE32+/COFF parser: sections, imports, entropy, overlay, Authenticode signature.

Detects packers through section entropy, missing or unusual imports, hidden overlays and unsigned binaries.

06

String extraction

Structure

Extracts ASCII and UTF-16LE strings and scores them heuristically.

The same data the PUA and network engines use: matching on both encodings, capped at 12 MB.

07

Heuristics

Behaviour

Suspicious combinations: hidden file, double extension, abnormal sizes.

It never decides alone — it adds context. A single signal is not a detection, which keeps false positives down on legitimate files.

Content

5

What is inside matters: nested archives, scripts, VBA macros and personal data that should not leave.

01

Archives

Container

Opens zip, tar, gzip, rar, 7z and apk and scans members recursively.

Members are decompressed and scanned separately. The archive itself is deliberately skipped by indicator engines to avoid random matches on compressed content.

02

Script deobfuscation

Behaviour

Deobfuscates PowerShell, VBScript and JavaScript: base64, char-codes, concatenation, -enc.

An obfuscated script stops being a black box: Malnox reconstructs the real text and evaluates it with the script-abuse rules.

03

VBA macros

Behaviour

Reads VBA projects from Office documents (OLE2) and evaluates them behaviourally.

AutoOpen, Shell, DownloadFromURL, macro triggers — the signals that matter, not merely the presence of a macro.

04

DLP

Data

Detects sensitive data: national IDs, Luhn-validated cards, private keys, tokens.

5 built-in policies (GDPR, PCI-DSS, secrets, HIPAA, confidential documents), each with a minimum match threshold and its own severity.

05

Emulation sandbox

Behaviour

Unwraps every encoded payload separately — up to 8 layers — and analyses what comes out.

The reason it exists: ordinary deobfuscation starts from the first recognised construct, so a decoy blob in front hides the rest. The sandbox enumerates every encoded region and unwraps each one independently. It does not run the file in a virtual machine.

Context

4

The signal signatures miss: where the link goes, which network indicators it carries, whether it is PUA or freshly written.

01

Web protection

Network

Extracts URLs and domains from files, matches them against the local blocklist, and writes dangerous domains into the hosts file so they can no longer be resolved.

Blocklist versioned by category: malware, phishing, c2, ransomware, botnet. Plus an explicit allowlist. No third-party reputation API. Blocking is real, not a label in the console: the domain is written to the hosts file on both IPv4 and IPv6, and the DNS cache is flushed after every change. Disabling it revokes the block and leaves the file exactly as it was.

02

PUA / adware

Quality

Pay-per-install networks, silent installs, offer flows, remote tools.

40 indicators in 5 groups, stored base64 in source so the host antivirus does not block compilation. 6 rules, all requiring a combination of signals.

03

Local reputation

Context

Hash prevalence in your own history, Authenticode signature, staging directory.

Built without VirusTotal. All 3 rules score below 25 on purpose — the engine is advisory and cannot trigger a verdict alone.

04

C2 indicators

Network

Dynamic DNS, tunnelling services, backdoor ports, in-memory download chains.

37 indicators in 4 groups. The engine resolves no DNS and opens no connections — it only reads what is written in the file.

Processes

1

Not part of the file pipeline: it reads the memory of already-running processes to catch payloads that never touch disk. It runs on demand, from the Memory page.

01

Memory scanner

Behaviour

Reads the resident pages of running processes and looks for indicators that never reach disk.

Run on demand, not continuously. Processes you cannot open — those of another user or system-protected — are reported as “skipped”, never as “clean”. Without a driver, a memory-only payload can escape if its process is protected.

Beyond scanning

What happens after detection

An antivirus that only shows an alert leaves the work on your desk. Malnox closes the loop: quarantine, incidents, rollback, audit.

Automatic response

When a file comes back malicious, Malnox does not settle for telling you. It stops the process holding the file first — with its child tree, so a dropper cannot continue from another process — then quarantines it. Essential Windows processes (csrss, winlogon, lsass, services, svchost, explorer) and reserved PIDs are never touched: the request is refused and written to the audit log. There is also a per-minute intervention cap, so a cascade of false positives cannot turn into a loop that closes everything.

Real-time protection

chokidar watches Downloads, Desktop and Documents. On startup it waits 10–12 s for the event volume to settle, then processes one at a time. When the verdict is malicious the process holding the file is stopped, the file goes to encrypted quarantine and, if the move fails, execution is denied through an ACL. You can also choose reporting only.

Encrypted quarantine

AES-256-GCM, SHA-256-derived key, 12-byte IV and 16-byte tag. On restore the tag is verified: a modified blob is refused. Files in the legacy DQ1 format stay restorable.

Ransomware guard

Six canary files checked every 60 s. When more than 40 writes land in a short window the suspect processes are frozen — left intact for analysis and resumable — then the copies taken before writing are restored automatically. Order matters: encryption is stopped first, repair comes second.

Incident queue

Every detection becomes an incident with triage, deduplicated by hash — the same file will not fill the list 40 times. State changes from the dashboard or the API.

Enterprise controls

admin / analyst / viewer roles enforced per route, scrypt passwords with salt, 32-byte tokens stored SHA-256 hashed, an append-only audit log and SIEM export with a bounded queue of 512 events.

Signed intel, with rollback

Intel packages are HMAC-SHA256 signed and applied atomically: stage in a temporary directory, then rename. Path traversal is rejected, and the previous version stays for /api/intel/rollback.

Transparent by construction

How scores combine

No engine has veto power and none can hide a verdict. The formula is simple and public.

final score = max(engines) + 15% × the sum of the rest

  • Maliciousscore ≥ 70 or any critical detection
  • Suspiciousscore ≥ 25 or any medium detection
  • Cleanbelow both thresholds, with every engine reported

The cap is 100. The report lists every engine, its score and its detections, so you can verify for yourself why a verdict came out the way it did.

Architecture decisions

Why it is built this way

Detection without a network

The product's core guarantee: no engine in the detection path makes a network request. Verifiable, not just promised.

  • Rules, lists and signatures in versioned local files
  • No DNS lookup during scanning
  • Works identically on an air-gapped workstation

Explainable verdicts

Every report shows which engine contributed what. There is no “trust us, we know better”.

  • Per-engine score alongside individual detections
  • Locally generated PDF report for every scan
  • YARA rules can be read, enabled or disabled

Response, not just alerts

When it finds something, Malnox acts: it stops the process, removes the file, freezes encryption and restores the backups. It does not just tell you and walk away.

  • The process holding an infected file is stopped before quarantine
  • An encryption attack is frozen, then the files are restored
  • AES-256-GCM quarantine with tag verification on restore
  • Essential Windows processes are never touched

Enterprise without SaaS

RBAC, append-only audit log, SIEM export and a hardening score — all on your own infrastructure.

  • scrypt + salt passwords, SHA-256 hashed sessions
  • admin / analyst / viewer roles enforced per route
  • Bounded SIEM queue: events drop, memory does not balloon

Privacy by default

The AI analyst is optional and advisory. By default it sends metadata only, and its answer never enters the verdict.

  • advisoryOnly = true, without exceptions
  • File content is sent only with aiSendContent
  • The API key is redacted in every response

Declared limits

The Malnox kernel driver compiles and signs, but it does not yet have the official Microsoft signature. We say so on the front page, not in a footnote.

  • A hardening score that treats “unknown” as unknown
  • Measured, not estimated, performance comparisons
  • Readable rules, not signatures hidden in a backend
The full flow

Four steps, no hidden steps

A scan sends the file through 17 independent engines, and the final verdict comes from a single coordinator.
  1. 01

    Install and scan immediately

    The installer is a single 177 MB file bundling the runtime, the MalNOX signature engine, YARA-X and the 67 rules. No account, no six-step wizard.

  2. 02

    The file runs through 16 engines

    Hash, rules, PE structure, strings, archives, scripts, macros, network indicators, emulation sandbox. Each engine writes its own independent score.

  3. 03

    Scores combine in the open

    The maximum plus 15% of the rest. Malicious at ≥ 70 or a critical detection, suspicious at ≥ 25 or a medium detection. Nothing hidden.

  4. 04

    You choose the action

    Report, quarantine with encryption, or open an incident. In real time, the action is configurable per installation.

Who it is for

Real situations, not imaginary personas

For home

The machine you bank on

Real-time protection on Downloads, Desktop and Documents, ransomware guard with rollback, and alerts on every detection. Without sending your filenames anywhere.

For freelancers

Contracts that contain personal data

The GDPR DLP policy catches national IDs, IBANs and phone numbers before you send the wrong file to the wrong client.

For IT teams

Endpoints that cannot talk to the cloud

Roles, append-only audit, SIEM export and HMAC-signed intel packages, applied offline through an activation file.

01

Hash

Signatures

SHA-256 and MD5 against the local signature database.

The first and cheapest gate: if the hash is known, the verdict is instant without opening the file.

02

YARA (own engine)

Rules

Own parser and evaluator for YARA syntax, with needle prefiltering.

Supports text with nocase/wide/ascii/xor/fullword, hex with wildcards and jumps, regex, any/all/n of them conditions, offsets, filesize and uint16(0).

03

YARA-X

Rules

YARA-X over the bundled 10-file .yar package, with ndjson output.

Independent from the in-house implementation: if the two disagree, you see it in the report.

04

MalNOX Core Engine

Signatures

MalNOX signature engine with the signature database shipped in the package.

Runs locally, with no cloud updates in the detection path. Signatures update through signed packages.

05

PE analysis

Structure

PE/PE32+/COFF parser: sections, imports, entropy, overlay, Authenticode signature.

Detects packers through section entropy, missing or unusual imports, hidden overlays and unsigned binaries.

06

String extraction

Structure

Extracts ASCII and UTF-16LE strings and scores them heuristically.

The same data the PUA and network engines use: matching on both encodings, capped at 12 MB.

07

Heuristics

Behaviour

Suspicious combinations: hidden file, double extension, abnormal sizes.

It never decides alone — it adds context. A single signal is not a detection, which keeps false positives down on legitimate files.

08

Archives

Container

Opens zip, tar, gzip, rar, 7z and apk and scans members recursively.

Members are decompressed and scanned separately. The archive itself is deliberately skipped by indicator engines to avoid random matches on compressed content.

09

Script deobfuscation

Behaviour

Deobfuscates PowerShell, VBScript and JavaScript: base64, char-codes, concatenation, -enc.

An obfuscated script stops being a black box: Malnox reconstructs the real text and evaluates it with the script-abuse rules.

10

VBA macros

Behaviour

Reads VBA projects from Office documents (OLE2) and evaluates them behaviourally.

AutoOpen, Shell, DownloadFromURL, macro triggers — the signals that matter, not merely the presence of a macro.

11

DLP

Data

Detects sensitive data: national IDs, Luhn-validated cards, private keys, tokens.

5 built-in policies (GDPR, PCI-DSS, secrets, HIPAA, confidential documents), each with a minimum match threshold and its own severity.

12

Web protection

Network

Extracts URLs and domains from files, matches them against the local blocklist, and writes dangerous domains into the hosts file so they can no longer be resolved.

Blocklist versioned by category: malware, phishing, c2, ransomware, botnet. Plus an explicit allowlist. No third-party reputation API. Blocking is real, not a label in the console: the domain is written to the hosts file on both IPv4 and IPv6, and the DNS cache is flushed after every change. Disabling it revokes the block and leaves the file exactly as it was.

13

PUA / adware

Quality

Pay-per-install networks, silent installs, offer flows, remote tools.

40 indicators in 5 groups, stored base64 in source so the host antivirus does not block compilation. 6 rules, all requiring a combination of signals.

14

Local reputation

Context

Hash prevalence in your own history, Authenticode signature, staging directory.

Built without VirusTotal. All 3 rules score below 25 on purpose — the engine is advisory and cannot trigger a verdict alone.

15

C2 indicators

Network

Dynamic DNS, tunnelling services, backdoor ports, in-memory download chains.

37 indicators in 4 groups. The engine resolves no DNS and opens no connections — it only reads what is written in the file.

16

Emulation sandbox

Behaviour

Unwraps every encoded payload separately — up to 8 layers — and analyses what comes out.

The reason it exists: ordinary deobfuscation starts from the first recognised construct, so a decoy blob in front hides the rest. The sandbox enumerates every encoded region and unwraps each one independently. It does not run the file in a virtual machine.

17

Memory scanner

Behaviour

Reads the resident pages of running processes and looks for indicators that never reach disk.

Run on demand, not continuously. Processes you cannot open — those of another user or system-protected — are reported as “skipped”, never as “clean”. Without a driver, a memory-only payload can escape if its process is protected.

Beyond files

Eight new modules for the state of the machine

File scanning says whether a file is dangerous. The other half is the state of the system: old versions, camera permissions, open firewall rules, disabled mitigations.

Vulnerability scanner

Tells you which installed programs run versions with known problems, so you can update them before someone uses them against you.

The catalogue is ours and it is small: it covers the applications commonly found on a Romanian machine, not the whole CVE database. An “unknown” result appears when the version cannot be parsed — it is never rounded up to “fine”.

Privacy Guard

Shows which applications were granted access to your camera or microphone, and whether they used it recently.

Windows does not write a “last used” stamp on every build. When it is missing we report it as absent rather than inventing a date. The module does not block the camera: it shows you the permissions so you can revoke them yourself in Settings.

Firewall audit

Checks your Windows Firewall rules and flags the risky ones: a port open to everyone, a program living in a folder anyone can write to.

The module is strictly read-only: it neither creates nor deletes rules, because a wrong firewall change can cut you off the network. It tells you what needs fixing and you decide.

Exploit Protection

Shows whether the Windows mitigations that make a bug harder to exploit — DEP, ASLR, CFG, ACG — are on, both system-wide and per application.

Values Windows does not expose stay “unknown” instead of becoming “pass”. You can apply a baseline for the watched applications, but every change is written to the audit log.

Email Guard

Opens a saved .eml or .msg message and tells you whether it carries dangerous attachments, phishing links, or a sender who is not who they claim to be.

It does not connect to your mailbox: it scans files, not an IMAP account. The SPF/DKIM/DMARC checks read what the receiving server wrote — if the header is missing, the result is “unknown”, not “authentic”.

USB Guard

Lists the attached USB sticks and external drives, checks whether they carry an `autorun.inf`, and finds executables dropped in the root.

Without a signed driver we cannot block a device from mounting: we scan what is on it. AutoRun is disabled by default on Windows 10 and 11 anyway — the check still matters where it has been re-enabled.

Banking mode

While you are on a payment page, checks whether the domain imitates a known bank and whether the page asks for sensitive data somewhere unusual.

HTTPS does not mean “legitimate merchant”, and we do not pretend it does. A correctly spelled domain with a valid certificate passes even if the shop is dishonest — the module reduces risk, it does not remove it.

Security Health Check

One score, in plain language, that gathers everything we know about your machine and tells you exactly what is worth fixing first.

An “unknown” or “off” area scores zero, not half, while “attention” scores half. The score can therefore drop when a check cannot be performed — that is the intent.

Try it on a file you already have.

The installer is 177 MB and asks for no account. Not convinced? Check a link above — the web engine is already running on this page.