DemonGoddess

I'm getting the same results from AVG, Norton and URLVoid as I have been, that the site is clean. All browsers I checked with, except Chrome are now loading without issue. The other browsers that loaded fine now are Firefox, Internet Explorer, Safari, and Opera. Chrome is now detecting the Java used in the archive menu as being malicious code, but that code hasn't been changed in years. The newest Java is in the RTE, and that is ALSO unchanged since it was added in February. It appears that we had someone try to hack in through the banner software in the early hours (for me) between roughly 2 am and 4 am EDT. So, to get around that, what I did was a fresh install, new database tables and a new user for the db for this particular software. I then deleted all the old stuff. This will hopefully fix it all. Last step, is waiting for Google to do a review. As they do it on PDT, I expect that won't happen until around 2 or 3 am my time.

Not a problem. I'm just waiting for Google to do a rescan so they remove the warning now.

30 minutes isn't so bad.... I've been working on straightening the mess out for ten solid hours now

...and... Someone tried to hack the banner software, which is what's doing this now. So I am doing a clean install of it, having the hosting company check again to be sure that nothing escaped, and then doing some stuff with Google webmaster tools. I do have users telling me Teatimer and Malwarebytes are finding nothing, and I know Kaspersky is finding nothing as I use it.

Looks like someone is trying to set this up via an unused subdirectory. I'm taking care of that now.

I'll have everything rechecked again, to be safe.

I just checked documentation (quick check going back a couple weeks) and am not finding this story in the mod work sheet. Nor am I finding this title as something deleted due to being written by an underage user.

There was direct copy/paste of content from the published book. This is why the story and user were deleted.

I think it kind of depends what part of the US you're from, as to whether or not one will keep personal information private or not. Also has a great deal to do with the age of the user as well. For example, most women in my age group, from the Midwest, keep their personal stuff to themselves. It's nobody's business but mine, ya know. And that is the attitude that makes that happen.

Domain scans from well known AV vendors, done now AVG shows as "currently safe" Norton shows as "ok" UrlVOID shows clean, except for MyWOT, and that is a content warning, as the site is an adult content site.

The same applies to visual stuff, actually. This is why some things I've drawn will only ever stay in my sketch book.....

What I would do, is a couple things here. One, make sure your Java is up to date. If it's not, it often will make you get that kind of error. Two, if you have toolbars, get RID of them. Toolbars are vulnerable, will often piggyback nasties in to your system, and spoof a site you visited. Finally, if you're using IE (although I see you're using firefox), ActiveX is an issue. ActiveX has ALWAYS been an issue. It makes it so that Trojans and the like easily find a way in to your system. Again, because people who write this garbage piggyback their malware in to the ActiveX controls, spoofing them. You also need to be sure that your BROWSERS are up to date. If you don't choose to use FF 4.x, as many people don't, then I'd go to Chrome, Opera, or Safari. Browsers not kept up to date are vulnerable as well. Rechecked everything, still shows clear on my end. Checked all the paths that could be affected as well. Where were you trying to go in the site?

I pm'd you with instructions. Turns out you'd entered the wrong name as your login name. As to the bad english, not a problem! Might TAKE us a while to muddle through with each other, but we'd get there.

added

The site is now in queue at Norton Safeweb to be retested, and is currently showing as "untested"

and more

I'm sure the author had a good reason FOR deleting those stories. Kindly read the statement that heads the forum, please.

Something else to keep in mind, is that we have a dedicated server, meaning that we share space with no one but ourselves for the hardware. At this point, as it's very easy to use, I'd recommend switching to Chrome for your browser. I'll keep my opinions of Norton to myself, as many of you like it. However, I use Kaspersky, and it has found absolutely NOTHING. Considering where I often end up when researching things FOR the site, if there was a problem, Kaspersky would've found it. It always does when I'm researching. This is NO different.

Okay, before I start posting up the screens, here are the steps I've taken on the client side: Ran an external scan, checking for issues, using two different services Checked each and every file for changes that I did not previously make I had the hosting company (Nexcess), check the physical hardware as well. That was the slowness yesterday. It took several hours to complete, as there is roughly 9.5GB of data (between all the databases) to scan, as well as the physical program files, graphics, and etc. Nexcess found NOTHING. Rechecked with Google's Safe Browsing diagnostics today. Results here. Submitted a dispute with Norton SafeWeb. Screens of what I did not find. Meaning there are no infections. Thursday Friday (yesterday) One of the subdomains I have more, but this is enough on the screen end I think. In the meantime, it appears that IE is having issues with Ajax again. I would also suggest to anyone getting this error, to disable any toolbars. Those things are prone to infection, and then spoof clean site addresses when trying to infect your machine.

La Clemenza Di Tito - Mozart

Make Me Smile - Chicago

This will likely occur from now for the next few hours, up until approximately 8 pm EDT, as the hosting company's technicians are running an intensive virus scan on the physical hardware at my request.

This is one of MANY stories I have to fix, from the crash in 2005. It will get done, eventually.

The story was deleted because the user who posted it was under eighteen years of age at the time of posting

added