SUDO is causing entries in the console log. A Virus?

Question

Hello,
I was looking through my OSX installation and I found this mysterious file placed in my Application Support Folder in my library:
username/library/application support/7103555
It is named "7103555" and it is a Unix Executable File (according to "Get Info")
I am worried it might be a virus. I don't recall putting it there. The only time I used terminal so far was to open a Profile Manager for Mozilla Thunderbird. I see that it mentions PrinterNotification and I do recall installing an HP printer driver. Is that where it might have come from. Is this normal? May I delete it? Should I reset something back in console? I am not sure what to do here.
Should I be concerned?
Thank you for any advice.
This is what it looks like when I open it:
cd /System/Library/SystemConfiguration/PrinterNotifications.bundle/Contents/MacOS
# SUDO is causing entries in the console log making me believe
# that it's not getting run correctly. I am removing SUDO from the
# command lines.
#sudo ./makequeues -u
#sudo ./makequeues -r
./makequeues -u;./makequeues -r&
exit 0

Answer 1

Mulder,
<<sarcasm mode on>>
You got me there: I can't even spot a simple shell script and figure out what it does and why. Nor could I explain it in plain 'Merican English to poor ol' rainforest. Nope, I must have absolutely no idea what I'm talking about.
<<sarcasm mode off>>
HINT: This is well within my area of expertise.
To quote one of your compadres, who "borrowed" it from answers.com:
"computer virus n. A computer program that is designed to replicate itself by copying itself into the other programs stored in a computer. It may be benign or have a negative effect, such as causing a program to operate incorrectly or corrupting a computer's memory."
A little further on in the same page:
"Virus
Software used to infect a computer. After the virus code is written, it is buried within an existing program. Once that program is executed, the virus code is activated and attaches copies of itself to other programs in the system. Infected programs copy the virus to other programs."
and
"Viruses Must Be Run to Do Damage
A virus is not inserted into data. It is a self-contained program or code that attaches itself to an existing application in a manner that causes it to be executed when the application is run."
On to Leap-A, from the description in Macworld (edited for brevity and clarity):
"...[W]hen you try to launch the newly-infected application, an apparent bug ... in the code prevents it [the application] from launching. But, ... a lot just happened:
A Spotlight search for the most-recently-used user-owned applications is run, and ... up to four of those programs at a time are infected...
The above process will repeat each time you try to launch an infected application."
The process described above fully conforms to the definition. Therefore, your, uh, "1337" assertion is wrong: Leap-A IS a virus.
-Wayne
PS I'll even make a more radical assertion: The first OS X viruses were written in 1983 by Fred Cohen. My source? Professor Cohen (after all, he invented the computer virus), who told me, "the first viruses written for the original experiments run on current Mac OSX systems without even a recompilation."