VirusTotal and MalwareBazaar, on your own keys
Malware lookups on scan findings now run on keys you connect under Integrations, count against your own accounts, and stay in your tenant. The shared keys they used to run on were free keys, and neither VirusTotal nor abuse.ch licenses those for a commercial service. Every match now also names the author of the rule that made it.
When a scan matches a rule on a file, the finding is more useful if it can also say whether that exact file is known malware. Until today, Wegweiser asked two malware databases about every flagged file in every tenant, on shared keys: MalwareBazaar, which says whether a file is a catalogued sample and which family it belongs to, and VirusTotal, which says how many antivirus engines flag it. From today, both are integrations: they run on keys you connect, or not at all.
Why it changed
Both shared keys were free keys, and both providers keep free keys out of commercial use. VirusTotal's terms say a public key must not be used in commercial products or services. abuse.ch, which runs MalwareBazaar, changed its terms in November 2025: free access is for not-for-profit purposes, and a business needs a subscription, which Spamhaus manages. A service an MSP runs for its clients is commercial.
The VirusTotal key was also too small: the fleet flags around 590 distinct files a day, and a public key allows 500 lookups. On Saturday night it ran out, and every lookup after that came back refused.
A platform licence covering every tenant would have to be paid for by every tenant, including the ones who already hold a licence of their own. So each is yours to connect instead.
Connecting them
Under Integrations > MalwareBazaar, paste the Auth-Key from your abuse.ch account (auth.abuse.ch) and confirm it is licensed for commercial use. The page links to Spamhaus for the subscription. Under Integrations > VirusTotal, paste a VirusTotal premium or Google Threat Intelligence key and make the same statement. Each statement is recorded with your name and the time, because neither provider says which kind of key a key is. A VirusTotal key whose allowance looks like the free tier's is named as such on the page.
From then on:
- Findings carry the verdicts: a catalogued sample and its family from MalwareBazaar, and how many engines flag the file from VirusTotal.
- Once a day, MalwareBazaar's newest samples are checked against the programs on your machines. That finds a known bad file no scan has reached. Your feed is checked against your machines only.
- Only the file's SHA-256 hash is sent. The file never leaves the machine.
- Lookups count against your accounts, capped at a daily limit you set. Each file is asked about at most once a day on MalwareBazaar and once a week on VirusTotal, and a flagged file is remembered for a month.
- If a provider refuses more lookups, they pause until it would accept them again, rather than asking with every scan.
- The answers are shown to your tenant and nobody else's. Disconnecting removes the key and every answer it paid for.
If you do not connect them
Nothing else about scanning changes. The same rules run on the same schedule, findings say which rule matched and on which file, and the analysis reads them the same way. Findings just no longer carry an outside verdict.
Every match names who wrote its rule
Most of the rules the scanner runs come from the security community, and most of those are licensed on one condition: whoever shows you a match names the author of the rule behind it. Wegweiser kept that name on every rule and showed it nowhere. Now it is on the match itself, in Detections, on the scanner overview and on the device's scan log, and What we look for says where the rule sets come from.
And the rules nobody licensed are gone
The community package the scanner draws on gathers rules from dozens of public repositories. Most say how their rules may be used; 432 of them came from repositories that say nothing at all, and a rule with no licence is not one anybody gave us the right to ship. They were removed from the scanner today. The 4,678 that remain are all published under open licences, and every future update of the package is filtered the same way before anything reaches a machine.