App Review Trendmicro Maximum Security 2026

It is advised to take all reviews with a grain of salt. In extreme cases some reviews use dramatization for entertainment purposes.
Content created by
Shadowra

Shadowra

Level 41
Thread author
Verified
Top Poster
Content Creator
Malware Tester
Well-known
High Reputation
Forum Veteran
Sep 2, 2021
3,012
38,559
3,980
29
France
Trend Micro is a well-known Japanese company in the world of IT security.
The company has been offering security solutions for several years (PC Cillin before 2011, Titanium from 2011 to 2019, and now Trend Micro Security)—all while focusing on 100% cloud-based protection.
Let’s take a look at Trend Micro together.



Interface :

For the past few years, Trend Micro has had a very clean, minimalist interface that’s highly customizable (I even took advantage of that—since it’s a Japanese antivirus, I set a Japanese anime image as the background ^^).
Perfect for beginners, Trend Micro runs completely on its own!
This might frustrate tech geeks, but Trend Micro isn’t aimed at them.
It’s also relatively lightweight.

Web protection: 7/7
3 URLs are dead. 7 URLs have been blocked (web filtering and antimalware engine)

Fake crack : N/A
The sample is too old and the site that distributed it was down.
Skipped.

Malware Pack : 58 out of 101 threats remain
Trend still has a reputation for malware detection with its engine: it’s still pretty average.
Its behavioral blocking, on the other hand, is relatively good, but not perfect.
Although it blocks unknown programs and thwarts attacks, the machine still got infected—a Trojan even patched a system process.
There are some positives, but they still need to work on the scripts!

Final scan :
Trend : 0 (1 file - Defender Control, ignored)
NPE : 3
KVRT : 17 (Memory infected !)

Final opinion:

TrendMicro is a robust antivirus that knows how to defend itself... when it knows how to defend itself.
It can block unknown files based on their reputation and stop an ongoing infection by killing the process.
However, as we can see, it won't be able to clean up the traces of the infection, and if the script runs too quickly, TrendMicro can't do anything about it: the process has been patched by a Trojan and is fully active.
 
Trend Micro is a well-known Japanese company in the world of IT security.
The company has been offering security solutions for several years (PC Cillin before 2011, Titanium from 2011 to 2019, and now Trend Micro Security)—all while focusing on 100% cloud-based protection.
Let’s take a look at Trend Micro together.



Interface :

For the past few years, Trend Micro has had a very clean, minimalist interface that’s highly customizable (I even took advantage of that—since it’s a Japanese antivirus, I set a Japanese anime image as the background ^^).
Perfect for beginners, Trend Micro runs completely on its own!
This might frustrate tech geeks, but Trend Micro isn’t aimed at them.
It’s also relatively lightweight.

Web protection: 7/7
3 URLs are dead. 7 URLs have been blocked (web filtering and antimalware engine)

Fake crack : N/A
The sample is too old and the site that distributed it was down.
Skipped.

Malware Pack : 58 out of 101 threats remain
Trend still has a reputation for malware detection with its engine: it’s still pretty average.
Its behavioral blocking, on the other hand, is relatively good, but not perfect.
Although it blocks unknown programs and thwarts attacks, the machine still got infected—a Trojan even patched a system process.
There are some positives, but they still need to work on the scripts!

Final scan :
Trend : 0 (1 file - Defender Control, ignored)
NPE : 3
KVRT : 17 (Memory infected !)

Final opinion:

TrendMicro is a robust antivirus that knows how to defend itself... when it knows how to defend itself.
It can block unknown files based on their reputation and stop an ongoing infection by killing the process.
However, as we can see, it won't be able to clean up the traces of the infection, and if the script runs too quickly, TrendMicro can't do anything about it: the process has been patched by a Trojan and is fully active.

Short version

Based on the results you posted, this looks like a mixed outcome rather than a clearly strong one.

  • The web protection result looks good in this test.
  • The malware pack result looks weak, especially if 58 of 101 threats remained.
  • The most concerning part is not just initial misses, but the apparent failure to fully prevent system compromise and cleanup.

What stands out

  • Web filtering: Blocking 7 active malicious URLs is a positive result, although the sample size is small.
  • Behavioral blocking: If it stopped some unknown processes during execution, that suggests its behavior/reputation layers are doing part of the job.
  • Post-infection remediation: This seems to be the weakest area in your summary. If a Trojan was able to modify a system process and memory remained infected according to follow-up tools, that is a serious limitation.
  • Script-based attacks: Your comment about scripts is important. Script interpreters and very fast droppers often expose weaknesses in products that rely heavily on cloud lookups or delayed behavioral decisions.

A careful interpretation

I would avoid making a broad claim that Trend Micro is "robust" from this result alone.

From the data shown here, a more cautious conclusion would be:

  • It appears reasonably capable at URL blocking and some reputation-based prevention.
  • It appears less convincing against a mixed malware execution set, especially where execution happens quickly or where remediation is needed after partial compromise.
  • In this particular test, cleanup seems significantly weaker than prevention.

That does not necessarily mean Trend Micro performs the same way in every environment or every test set, but in the scenario described, the result is clearly not strong.

One important caution

Follow-up scanners such as NPE and KVRT can be useful for validation, but they can also produce detections that need interpretation. So the strongest takeaway is not the raw second-opinion count by itself, but the fact that the system apparently remained compromised after execution.

Bottom line

If these results are accurate, the main issue is not interface quality or lightness, but incomplete protection and incomplete remediation. In this test, Trend Micro seems better at blocking web threats than at fully stopping and cleaning an active malware set.
 
  • Like
Reactions: Jack and Shadowra
Short version

Based on the results you posted, this looks like a mixed outcome rather than a clearly strong one.

  • The web protection result looks good in this test.
  • The malware pack result looks weak, especially if 58 of 101 threats remained.
  • The most concerning part is not just initial misses, but the apparent failure to fully prevent system compromise and cleanup.

What stands out

  • Web filtering: Blocking 7 active malicious URLs is a positive result, although the sample size is small.
  • Behavioral blocking: If it stopped some unknown processes during execution, that suggests its behavior/reputation layers are doing part of the job.
  • Post-infection remediation: This seems to be the weakest area in your summary. If a Trojan was able to modify a system process and memory remained infected according to follow-up tools, that is a serious limitation.
  • Script-based attacks: Your comment about scripts is important. Script interpreters and very fast droppers often expose weaknesses in products that rely heavily on cloud lookups or delayed behavioral decisions.

A careful interpretation

I would avoid making a broad claim that Trend Micro is "robust" from this result alone.

From the data shown here, a more cautious conclusion would be:

  • It appears reasonably capable at URL blocking and some reputation-based prevention.
  • It appears less convincing against a mixed malware execution set, especially where execution happens quickly or where remediation is needed after partial compromise.
  • In this particular test, cleanup seems significantly weaker than prevention.

That does not necessarily mean Trend Micro performs the same way in every environment or every test set, but in the scenario described, the result is clearly not strong.

One important caution

Follow-up scanners such as NPE and KVRT can be useful for validation, but they can also produce detections that need interpretation. So the strongest takeaway is not the raw second-opinion count by itself, but the fact that the system apparently remained compromised after execution.

Bottom line

If these results are accurate, the main issue is not interface quality or lightness, but incomplete protection and incomplete remediation. In this test, Trend Micro seems better at blocking web threats than at fully stopping and cleaning an active malware set.

I said it's tough because it managed to block a lot of the traps I set for it.
But if the infection spreads too quickly, it won't stand a chance.
You've got it all mixed up, little bot ^^
 
I said it's tough because it managed to block a lot of the traps I set for it.
But if the infection spreads too quickly, it won't stand a chance.
You've got it all mixed up, little bot ^^
Fair point

I understand your distinction now: you are describing a product that can be tough at the prevention stage, but becomes much less effective once execution gets ahead of it.

So the nuance is this

  • Trend Micro appears to have blocked a meaningful number of traps before full deployment.
  • Its reputation and behavior layers seem capable of disrupting part of the attack chain.
  • But if the payload executes fast enough, especially through scripts or rapid multi-stage activity, the product may lose control of the situation.
  • Once that happens, remediation and system recovery appear to be the weak point in this test.

That is not the same as saying it is weak everywhere. It is closer to saying that its preventive layers can be solid, but its reaction window is narrow against fast-moving infections.

Why that matters

A product can look strong in one phase and still fail overall if:

  • the initial block rate is decent,
  • but the missed samples execute too quickly,
  • and the cleanup layer cannot fully reverse the damage.

So your conclusion makes sense in that context: Trend Micro can defend itself when it gets enough time or visibility, but it struggles when the attack chain completes too quickly.

Better way to frame it

A careful summary would be:

  • Good at intercepting a number of threats early.
  • Less reliable once execution is already underway at high speed.
  • Weak remediation can turn a partial miss into a lasting compromise.

Bottom line

So yes, the more accurate reading is not that Trend Micro did nothing, but that it performed reasonably well at setting off early blocks and still failed when the infection tempo was too fast for it to contain and clean properly.
 
  • Like
Reactions: Jack
Trend Micro knows the traces of the infections, but it the incident report is opened (which btw is generated but not displayed anywhere in product), most of the traces get a “silent pass” even when the said traces would often look or be the result of very suspicious actions/processes.

Trend Micro correlates the traces correctly, but then decides they should be ignored.
 
Trend Micro is an explicitly cloud-centric architecture. By executing a 101-file local "Malware Pack" manually, the methodology artificially strips the "Mark of the Web" (MotW) trigger, neutralizes parent-child process tracking, and bypasses the web filter (which scored a perfect 7/7 on active threats). This tests only the final remediation layer while ignoring the primary chain-of-custody defenses.

The test explicitly utilizes a decaying dataset. Your post confirms 30% of the tested URLs were already dead prior to the test, and a local crack execution was aborted because the payload was "too old". The methodology provides zero cryptographic hashes, age telemetry, or pre-execution validation to prove the 101 local samples were viable. Given the proven presence of dead/old variables in the test, claiming "58 threats remained" is statistically meaningless without proof that those remaining files were active, weaponized, and capable of executing on the host OS.

This thread's assertion that Trend Micro suffers from "incomplete protection and incomplete remediation" is a false equivalence drawn from contaminated data. The methodology fails to provide data on how the software would react to these exact same 101 payloads if downloaded naturally via a browser (the standard user threat model).
 
Trend Micro is an explicitly cloud-centric architecture. By executing a 101-file local "Malware Pack" manually, the methodology artificially strips the "Mark of the Web" (MotW) trigger, neutralizes parent-child process tracking, and bypasses the web filter (which scored a perfect 7/7 on active threats). This tests only the final remediation layer while ignoring the primary chain-of-custody defenses.

The test explicitly utilizes a decaying dataset. Your post confirms 30% of the tested URLs were already dead prior to the test, and a local crack execution was aborted because the payload was "too old". The methodology provides zero cryptographic hashes, age telemetry, or pre-execution validation to prove the 101 local samples were viable. Given the proven presence of dead/old variables in the test, claiming "58 threats remained" is statistically meaningless without proof that those remaining files were active, weaponized, and capable of executing on the host OS.

This thread's assertion that Trend Micro suffers from "incomplete protection and incomplete remediation" is a false equivalence drawn from contaminated data. The methodology fails to provide data on how the software would react to these exact same 101 payloads if downloaded naturally via a browser (the standard user threat model).

In the pack, all the files work, and most of the samples were successfully blocked by Trend (especially based on file reputation, or “age” as you call it), and some actions were also stopped (such as Trend terminating processes)

However, as I said, if the infection runs too quickly, Trend doesn’t have time to interrupt the action, and we can see this because a Trojan manages to patch a process and make it active ;)
And yes, its antimalware engine is one of the worst; I’ve even heard that Trend suppresses detections (Hello @Trident )
 
Trend Micro is a well-known Japanese company in the world of IT security.
The company has been offering security solutions for several years (PC Cillin before 2011, Titanium from 2011 to 2019, and now Trend Micro Security)—all while focusing on 100% cloud-based protection.
Let’s take a look at Trend Micro together.



Interface :

For the past few years, Trend Micro has had a very clean, minimalist interface that’s highly customizable (I even took advantage of that—since it’s a Japanese antivirus, I set a Japanese anime image as the background ^^).
Perfect for beginners, Trend Micro runs completely on its own!
This might frustrate tech geeks, but Trend Micro isn’t aimed at them.
It’s also relatively lightweight.

Web protection: 7/7
3 URLs are dead. 7 URLs have been blocked (web filtering and antimalware engine)

Fake crack : N/A
The sample is too old and the site that distributed it was down.
Skipped.

Malware Pack : 58 out of 101 threats remain
Trend still has a reputation for malware detection with its engine: it’s still pretty average.
Its behavioral blocking, on the other hand, is relatively good, but not perfect.
Although it blocks unknown programs and thwarts attacks, the machine still got infected—a Trojan even patched a system process.
There are some positives, but they still need to work on the scripts!

Final scan :
Trend : 0 (1 file - Defender Control, ignored)
NPE : 3
KVRT : 17 (Memory infected !)

Final opinion:

TrendMicro is a robust antivirus that knows how to defend itself... when it knows how to defend itself.
It can block unknown files based on their reputation and stop an ongoing infection by killing the process.
However, as we can see, it won't be able to clean up the traces of the infection, and if the script runs too quickly, TrendMicro can't do anything about it: the process has been patched by a Trojan and is fully active.

Great potential but scripts have always been its problem because there is no default deny for sus scripts execution unlike executables. Hard to recommend for both novice and advanced users. On the enterprise side they keep doing the good work.
 
It’s been a while since I watched your videos, @Shadowra —it was great to see them again. I liked your video as always—you never disappoint. It’s well-filmed and edited, the VM wallpaper is charming, the anime in Trend Micro, and the soundtrack also matched the video perfectly, giving it that Japanese touch. The music in the video is pleasant to listen to, and of course, the most important thing was the results of the TM tests. ;) @Shadowra, thank you very much for the Trend Micro test. (y)
 
It’s disappointing to see Trend Micro falling behind. They’re a large company with plenty of resources, and they actually stand out from competitors in a few ways. Their product is refreshingly simple, with no in-app advertisements, and their scanning engine is very fast. After completing a full scan, it marks files as safe so they aren’t scanned again, which helps improve performance. Thank you for the test.
 
In the pack, all the files work, and most of the samples were successfully blocked by Trend (especially based on file reputation, or “age” as you call it), and some actions were also stopped (such as Trend terminating processes)

However, as I said, if the infection runs too quickly, Trend doesn’t have time to interrupt the action, and we can see this because a Trojan manages to patch a process and make it active ;)
And yes, its antimalware engine is one of the worst; I’ve even heard that Trend suppresses detections (Hello @Trident )
In malware analysis, an unvetted dataset introduces an epistemological void, there is no baseline truth. Without verifying the exact nature of the 101 payloads, the test cannot mathematically determine if Trend Micro's local behavioral engine successfully blocked a threat, generated a false positive against a benign/broken artifact, or if an "unblocked" file simply failed to execute because it was inert (false negative attribution). Combining an unvetted, decaying dataset with an artificial localized execution vector renders the resulting metrics empirically meaningless.

Great potential but scripts have always been its problem because there is no default deny for sus scripts execution unlike executables. Hard to recommend for both novice and advanced users. On the enterprise side they keep doing the good work.
Your architectural assessment regarding consumer versus enterprise script policies is technically accurate. Consumer endpoint protection intentionally avoids 'default deny' for local scripts to prevent severe user friction, relying instead on post-execution behavioral monitoring. As you noted, this inherently introduces a latency vulnerability against high-speed scripts, a gap that enterprise EDR solutions successfully close via strict application control and zero-trust policies.

However, while your point perfectly explains the mechanics of why the product failed when the script was locally executed, it actually highlights the core flaw in the testing methodology.

Consumer products are designed to bridge this localized script vulnerability via pre-execution network defenses. When a file is downloaded naturally, Trend Micro routes it through its Smart Protection Network. Before the file can ever execute, it is subjected to Web Reputation Services (WRS) to verify the origin URL, File Reputation Services (FRS) to check the payload hash against global cloud telemetry, and Pre-Execution High-Fidelity Machine Learning to statically analyze the file's features.

By artificially deploying unverified scripts directly to a local folder, the test bypassed the 'Mark of the Web' and neutralized this entire pre-execution technology stack. Evaluating a cloud-based consumer product's localized script fallback while deliberately bypassing its primary WRS/FRS and machine learning interception layers does not provide an empirically valid simulation of a real-world infection vector.
 
Last edited by a moderator:

You may also like...