Initial commit

.gitignore

@@ -0,0 +1,5 @@
+.*
+!.gitignore
+build/
+dist/
+

CHANGELOG

@@ -0,0 +1,13 @@
+v1.2.0 [2021-07-26]
+- (Fix) External USB drives weren't being detected on Windows 10.
+
+v1.1.0 [2009-02-02]
+- (New) Suspected worm file extension list updated. Also removes any autorun.inf file found in the drive root.
+- (New) Now can detect the following file extensions: exe, cmd, bat, vb, vbs, vbe, vbscript, js, jse, ws, wsf, wsh, pif, scr, sct, script.
+
+v1.0.1 [2008-09-08]
+- (Fix) Newly attached mass storage devices weren't getting detected.
+
+v1.0.0 [2008-08-26]
+- First release.
+

LICENSE

@@ -0,0 +1,24 @@
+USB Worm Protection License
+
+Copyright (c) 2021 Sharafat Ibn Mollah Mosharraf
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, and/or sublicense the Software,
+and to permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+1. The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+2. If the source code is modified, the "About" section of the application shall
+include "Original Software Credit: Sharafat Ibn Mollah Mosharraf (www.sharafat.co.uk)".
+3. No commercial transactions are allowed. Therefore, the Software cannot be sold.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -0,0 +1,29 @@
+# USB Worm Protection
+USB Worm Protection provides you with an easy and highly efficient way to scan your hard
+disk and USB devices for computer worms. This reliable and intuitive piece of software
+is a great tool for every computer user that wants to protect their systems against
+these types of malware programs.
+
+USB Worm Protection is a simple-to-use program designed to rid your USB flash disks of
+files infected with worms. It packs several handy features that can be figured out even
+by users with little or no experience in antivirus systems.
+
+At initialization, the tool creates an icon in the system tray area, where you can access
+options and configure settings.
+
+Aside from scanning the USB flash disks, USB Worm Protection is also capable of scanning
+your local drives for worms. This process shows the total scanned, detected and suspected
+items, start and finish time, and duration. Every detected worm or suspected file can be
+deleted, skipped or sent to the quarantine.
+
+As far as program preferences go, you can enable silent scan mode, set the tool to prompt
+for an action against suspected files, and configure scan notification options (e.g. remove
+slide-in dialogs after the scan is done). A restart of USB Worm Protection is required to
+apply the new changes.
+
+The application uses a moderate-to-high amount of CPU and RAM, but it doesn't interrupt user
+activity, since it can run silently in the background, alongside other processes.
+
+[Description provided courtesy of Softpedia and Softoxi.]
+
+For more information, please visit [http://usbwp.sharafat.co.uk](http://usbwp.sharafat.co.uk)

build.xml

@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="USB_Worm_Protection" default="default" basedir=".">
+    <description>Builds, tests, and runs the project USB Worm Protection.</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties
+      -post-init:                called after initialization of project properties
+      -pre-compile:              called before javac compilation
+      -post-compile:             called after javac compilation
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-jar:                  called before JAR building
+      -post-jar:                 called after JAR building
+      -post-clean:               called after cleaning build products
+
+    (Targets beginning with '-' are not intended to be called on their own.)
+
+    Example of inserting an obfuscator after compilation could look like this:
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Another way to customize the build is by overriding existing main targets.
+    The targets of interest are: 
+
+      -init-macrodef-javac:     defines macro for javac compilation
+      -init-macrodef-junit:     defines macro for junit execution
+      -init-macrodef-debug:     defines macro for class debugging
+      -init-macrodef-java:      defines macro for class execution
+      -do-jar:                  JAR building
+      run:                      execution of project 
+      -javadoc-build:           Javadoc generation
+      test-report:              JUnit report generation
+
+    An example of overriding the target for project execution could look like this:
+
+        <target name="run" depends="USB_Worm_Protection-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that the overridden target depends on the jar target and not only on 
+    the compile target as the regular run target does. Again, for a list of available 
+    properties which you can use, check the target you are overriding in the
+    nbproject/build-impl.xml file. 
+
+    -->
+</project>

lib/nblibraries.properties

@@ -0,0 +1,16 @@
+libs.CopyLibs.classpath=\
+    ${base}/CopyLibs/org-netbeans-modules-java-j2seproject-copylibstask.jar
+libs.CopyLibs.displayName=CopyLibs Task
+libs.CopyLibs.prop-version=3.0
+libs.hamcrest.classpath=\
+    ${base}/hamcrest/hamcrest-core-1.3.jar
+libs.hamcrest.displayName=Hamcrest 1.3
+libs.hamcrest.prop-maven-dependencies=org.hamcrest:hamcrest-core:1.3:jar
+libs.junit_4.classpath=\
+    ${base}/junit_4/junit-4.13.1.jar
+libs.junit_4.displayName=JUnit 4.12
+libs.junit_4.javadoc=\
+    ${base}/junit_4/junit-4.13.1-javadoc.jar
+libs.junit_4.prop-maven-dependencies=junit:junit:4.13.1:jar
+libs.junit_4.src=\
+    ${base}/junit_4/junit-4.13.1-sources.jar

manifest.mf

@@ -0,0 +1,3 @@
+Manifest-Version: 1.0
+X-COMMENT: Main-Class will be added automatically by build
+