Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Window Shade

2 (16.7%)

Control Strip

0 (0%)

Apple Menu with Apps in it

3 (25%)

Special in Finderbar

0 (0%)

Old Window UI

7 (58.3%)

Total Members Voted: 12

[Syntho]

Is that taken from the Steinberg FTP?

[Jakl]

check my folder

[Syntho]

Is that a different file from what's on the Steinberg FTP?

[supernova777]

i didnt post the 5.2 file because it was listed as a "public beta" and was never taken officially out of beta status from what i could dedeuce.... its perfectly fine to use it tho im sure.

[Jakl]

Is that a different file from what's on the Steinberg FTP?

It must be - but I downloaded this a long time ago.

i didnt post the 5.2 file because it was listed as a "public beta" and was never taken officially out of beta status from what i could dedeuce.... its perfectly fine to use it tho im sure.

There is a read me that goes with it you can have a look at.

[MacTron]

I'll hope that Die Hard don't be offended if I quote myself from a PM I'd sent to him on May 16, 2014:

I have Sevendust/666 in two occasions. Now a days I don't have it in any of my systems, but it may be in to some very old compress file or disk image... 
... in the last infection, my suspicious origin was Steinberg FTP !

[Mat]

I´d like to share my findings when I had 666/Seven Dust a few years ago. Here is how I got rid of it:

• Installing Virex (I think 6.2 is the latest version)
• getting the latest Virus definitions from late 2007
• running the full scan and let Virex delete all 666
• And here comes the tricky part; 666 is writing itselve into the RAM, and copying to every program that gets opened/closed. That means that Virex can delete all copys of 666 at the HD, but when you close Virex 666 is writing itselve to the Virex program itselve. So when you are done with Virex, do not close Virex or shutdown the computer, just switch it OFF, and let it off for a minute or more.
• Scan again if you got and deleted all 666

[IIO]

yes, absolutely, that is a virus, or to be exact, a file infector.

as there are only 2 or 3 for OS9 it should be possible to find out his name.

please be quick, in case it is a 666 extension (and no, removing the extension will not work.)

[Syntho]

How did a poll get posted with this thread? I definitely didn't make that poll. Hmm...

[supernova777]

How did a poll get posted with this thread? I definitely didn't make that poll. Hmm...

probably mactron? or protools guy?



(Edited to keep personal users information privately)

[MacTron]

probably mactron? or protools guy?

I didn't do it.

[dr bu]

the 666virus did it he he

[Syntho]

I definitely didn't type those answers in there, I don't even know what a couple of those are. Let me try something...

[Syntho]

I thought I might have clicked New Poll when posting a thread and it fills out automatically if you don't fill anything in, but it says you must type in two responses and a question for it to go through. The only other person who can edit posts in this forum is DH I think.

[Protools5LEGuy]

probably mactron? or protools guy?

I didn't do it.

Neither do I

[supernova777]

the 666virus did it he he

LOL!

[IIO]

oh, when i posted this i didnt notive how long that threas already was and that the problem already had been found.

i hope you have done in between what has to be done? because if not, this extension will one day delete all your multimedia files on startup.

[Syntho]

Mactron removed the virus and replace the link 

I actually formatted my entire system, but I was planning to do that anyway.

[supernova777]

Guys, I've got some bad news. That Cubase VST/32 5.0 update file is infected with the 666/SevenDust virus. CubaseVST32_51r1.sit.bin is the file.

we need to figure out if this file was re-packaged by mactron back in april 2014
because that was when we were doing all this re-encoding of sit  + bin files
to ensure compatibility with a-drive... we need to find out if this is a solo file that is infected or if there are other files that were infected

[IIO]

one would think that this is impossible, someone has an infected file, and then distributes it further.

but it can easily happen.

because as long as you dont launch the infected app, it wont infect your system, so all you have to do is not running antivirus stuff in the right moment, and you keep such files for years without knowing.

which is why it is important for anyone to still keep ones own protection running ... also for a 12 years old OS.

the good thing about file infectors is that you notice it.

simpletext takes 4 second to start? that rang a bell. because that is exactly what i told my friends about 14 years ago when i caught this thing for the first time, too. i then learned about "antivirus" for macintosh ithin minutes.