Spam in my LJ

[giza]

This guy just spammed my LJ with an ad for Scotttrade. His IP is 12.164.16.88, which resolves to mr-min-16-88.dmisinetworks.com. To borrow a quote from postvixen, do whatever the F*CK with this that you want!

I base the charge of spamming on the following things:
- A throwaway address at hotmail was given as the preferred contact method. This is typical of spammers.
- The message itself was vague. It said that I had "talked about Scotttrade", which is not the case. golum had mentioned it in a comment, however. My guess is that they found this through Google.
- I checked out the user account. It has 1 friend, and 1 LJ entry, equally vague.

I think Scotttrade is getting a nastygram from me when I get home tonight. I suspect this guy was a spamming affiliate and that they themselves were unaware of this.

Comments

[whyrl.livejournal.com]

Assuming of course that box wasn't rooted.

[giza.livejournal.com]

Perhaps being disconnected by their ISP (http://slashdot.org/article.pl?sid=04/03/10/0738238&mode=nested&tid=111&tid=126&tid=172&tid=95) will give the owner of the infected/rooted machine a clue.

Spamming.

[cjthomas.livejournal.com]

A quote from bash.org comes to mind:

"I'm going to become rich and famous after I invent a device that allows you to stab people in the face over the internet."

It'd cut down on my university account's spam, that's for sure.

[khakiwolf.livejournal.com]

Hehe... spamming affiliate. Like that guy who likes to pretend he's "Wendy's Spokesperson"??

PS: Are you good with hardware/software? My Photoshop 6.0 keeps locking my computer up for no apparent reason and I don't know why. Any suggestions?

[giza.livejournal.com]

One thing that CAN happen is sometimes when hardware gets flaky, it'll be fine for normal use but crap out under high stress. Not that that Photoshop is CPU/memory intensive, or anything. Read here for a full explanation (http://www.bitwizard.nl/sig11/). Case in point tgeller once had a computer that ran Windoze NT fine. Then one day we installed Linux on it. The moment I tried to compile Apache, the box locked up. I could make a TCP connection to the machine, but not actually get back in. I called Tom and asked him to turn on the monitor, and was treated to, "There's all these hex codes on the screen". Hee.

Since you're not running Linux, I'm not sure how to go about stressing out your computer. Perhaps try downloading and running some benchmarking software on your computer? What you want to do is put your machine under high loads for an extended period of time and see what happens. If you can reliably reproduce the problem, then you can start changing out pieces of hardware (or messing with software settings) and see what effect these things may have.

[jdarkwulf.livejournal.com]

Just as a tip, I work for another ISP that snapped up a portion of the former @Home's users/assets/accounts. We all still use AT&T as a backbone connection. Despite us technically being their boss in the matter, we've lately been getting tons of mandates from them to block various accounts due to spamming and/or network traffic that seems virus-related.

So, it's not just Comcast, because AT&T's arm is longer in this matter than you'd think. And their interest seems to be in preventing this sort of activity. Hooray for our side, eh? :)

[smoke-au.livejournal.com]

Hi, I found this LJ thru a link from the LJ of a friend of mine and apparently yours at one point. "Shadeyraccoon".

Anyhow, with your friends issue compiling apache, or the photoshop issue, the problem is most likely the memory sticks. Photoshop uses memory sticks fairly intensively even if it doesnt use its capacity fully. gcc++ or any other standard compiler on Linux is also incredibly hard on the memory sticks and the symptoms described indicate that may be the cause. compiling the kernel on linux is a fantastic way to check that the memory on the box is in shape.