Filtration ♦ Item Filter Script Editor ♦ [ v1.2.2 ] ♦ Updated 2019-09-11

Great work with Filtration! It's amazing. I just added support for it in my filter and it's been great.

Also, if you could add it to the list of filter: MaskedChimp's Filter

Keep up the great work and I'll keep working to improve my Filtration support. :)

"

heavykiller wrote:

Great work with Filtration! It's amazing. I just added support for it in my filter and it's been great.

Also, if you could add it to the list of filter: MaskedChimp's Filter

Keep up the great work and I'll keep working to improve my Filtration support. :)

Done :)

There'll shortly be a minor update to change the maximum PlayAlertSound value from 100 to 300 as per the latest game patch.

New Release 2015-07-31 - 0.11

♦ Changed maximum PlayAlertSound volume from 100 to 300 as per latest patch
♦ The update check on startup was broken in 0.10 - this has now been fixed.
♦ Please note that this is the first auto-updated release since 0.9 and includes the async saving and loading changes from 0.10 which was not auto-updated in order to get feedback on stability (given the lack of complaints I'm going to assume everything's all good!). Check out the GitHub release page for the 0.10 release notes.

0.11 has been working well for me. Thanks Atom.

Hey, AtomYcX!

Just started using the program the other night to modify Neversink's loot filter, and it worked fantastically! So, thank you immensely for making a great program for visualizing and editing loot filters :D

Now, to the meat of the post. I returned to my computer just now to find that Microsoft Security Essentials is flagging Filtration.ThemeEditor.dll as VirTool:Win32/VBInject. I am uncertain why it would do that unless it's a false positive, but I just wanted to bring this to your attention. If this has been addressed previously, then please, disregard my post and press on! I will send you a PM about this as well to be sure that you get this info as it may affect others (maybe not?).

Thanks again!

-ph3nomz

"

ph3nomz wrote:

Hey, AtomYcX!

Just started using the program the other night to modify Neversink's loot filter, and it worked fantastically! So, thank you immensely for making a great program for visualizing and editing loot filters :D

Now, to the meat of the post. I returned to my computer just now to find that Microsoft Security Essentials is flagging Filtration.ThemeEditor.dll as VirTool:Win32/VBInject. I am uncertain why it would do that unless it's a false positive, but I just wanted to bring this to your attention. If this has been addressed previously, then please, disregard my post and press on! I will send you a PM about this as well to be sure that you get this info as it may affect others (maybe not?).

Thanks again!

-ph3nomz

Hey - thanks for raising this - it appears you aren't the only person having this issue as an issue has been raised on GitHub regarding this same problem. The fact that multiple people have reported this now confirms to me that it's definitely a false positive and not a case of some other malware infecting existing DLLs on the machine.

Here's the GitHub issue: https://github.com/ben-wallis/Filtration/issues/14

Are you using Windows 10 like the guy who raised the GitHub issue by any chance? Because I'm running Windows 7 with Microsoft Security Essentials and it doesn't detect anything on my machine (and I've got many copies of that DLL lying around from development builds / release packaging etc).

The Microsoft page about "VirTool:Win32/VBInject" says this:

"

A malicious file is generally encrypted/and or compressed and stored inside another program (written in Visual Basic), which decodes the malicious file and loads it.

The malicious program may be injected into a clean process or loaded in a new process of its own. Unlike a "dropper", the malicious executable is never written to disk as a separate file.

I can only assume at this stage that the fact that the ThemeEditor DLL performs serialization/de-serialization of .filtertheme files has somehow triggered the heuristics that match this definition in MSE as Filtration has neither obfuscation nor any Visual Basic code.

I've submitted the DLL via Microsoft's security site requesting that it be investigated as a false positive. For now all I can suggest is that you un-quarantine it in MSE and/or add an exception to the Filtration directory. I'll keep this posted updated with any more updates to this issue.

-AtomYcX

Damn, I didn't expect a response from Microsoft so quickly. This should now be fixed!

"

Microsoft wrote:

Analysis of the file(s) in Submission ID MMPC15080766905171 is now complete.

This is the final email that you will receive regarding this submission.

The Microsoft Malware Protection Center (MMPC) has investigated the following file(s) which we received on 8/7/2015 1:04:33 PM Pacific Time.
Below is the determination for your submission.

========
Submission ID MMPC15080766905171

Submitted Files
=============================================
Filtration.ThemeEditor.dll [Not Malware]


Analyst Comments
================
-- 8/7/2015 1:35:07 PM --
We have reviewed the file(s) and we have removed detection.

Fantastic! That's great news that it was fixed on Microsoft's end so quickly! I am glad that I could help in some way ;]

Thanks again, AtomYcX!

Hey,

Winows Defender on Windows 10 still assumes that your installer is

"

Trojan:Win32/Tefau.A!plock

http://www.microsoft.com/security/portal/threat/encyclopedia/entry.aspx?name=Trojan%3aWin32%2fTefau.A!plock&threatid=2147690360&enterprise=0

I dunno how to contact or anything. just want to inform you.

Cheers

"

Stielowned wrote:

Hey,

Winows Defender on Windows 10 still assumes that your installer is

"

Trojan:Win32/Tefau.A!plock

http://www.microsoft.com/security/portal/threat/encyclopedia/entry.aspx?name=Trojan%3aWin32%2fTefau.A!plock&threatid=2147690360&enterprise=0

I dunno how to contact or anything. just want to inform you.

Cheers

The installer? And not Filtration.ThemeEditor.dll? Is this filtration_0.11_setup.exe ?