Recently login my old CS:GO account and this happen
Non Prime
Sergeant Major Rank 18 (almost prime)
https://steamcommunity.com/profiles/76561199002293173
I used Osiris since Private Rank 2.
i don't know when this happen
Don't hack on accounts you care about, make smurf accounts and hack on those.
Don't hack on accounts you care about, make smurf accounts and hack on those.
This is my throwaway account . I just want to know what make this account detected by VAC.
K.A.R.M.A is bitch noob doggie. <3
This is not an Osiris problem. Close this issue.
lol
This is not an Osiris problem. Close this issue.
How can you be so sure? There's been a huge influx of bans for people using Osiris, and I don't believe it was associated with any ban wave. So, what's to blame if it's 'not Osiris'
This is not an Osiris problem. Close this issue.
How can you be so sure? There's been a huge influx of bans for people using Osiris, and I don't believe it was associated with any ban wave. So, what's to blame if it's 'not Osiris'
There are countless issues regarding bans. People rage, get OW and finally VAC ban.
VAC after Game Ban is very normal.
VAC after an OW ban is the behaviour that VACnet used to do, theres a chance that something osiris is doing is getting picked up by VACnet.
Or, VAC knows that you injected some shit. But it doesn't ban unless VAC is 100% sure it's a cheat. Once you get a game ban, it leaves no doubt that the injected shit was a cheat.
Right, well, I only ever used Radar (bSpotted) and every day I used it I customised the source code to really shake up the signature, by running an automation script which automatically renames functions, variables, switches order of operations (basically turns repeating functions into for loops and vice versa + randomisation, using #define to tell the program what to do and where), and also protecting my .dll's using code mutation and other shit for "safety".
So, by those means, I can exclude anything to do with signatures because it changes so drastically. So, what is left to be the cause of my bans.. hooking? SOMEHOW one of the features... ? what else can Osiris be doing? Have they hooked functions used by the csgo process to monitor them that we're unaware of? Big sad :(
The signature shake-up is joke. Aimware changes signature on every run and still Aimware users get banned in bulk every 6-9 months or so.
If you hack and you expect NO BAN then good luck.
The signature shake-up is joke. Aimware changes signature on every run and still Aimware users get banned in bulk every 6-9 months or so.
If you hack and you expect _NO BAN_ then good luck.
I, for one, never said I expected no ban.
Two, I don't see how anything I said referencing the signature shake-up was a joke...
If Aimware's signature changes enough on every run (which you're yet to prove), I doubt that people are getting banned plainly because of the signature, especially since there's, from what I know, zero proof on why Aimware users are banned in these waves.
Head here doggie: https://www.valvesoftware.com/fi/contact?contact-person=Gabe%20Newell
Head here doggie: https://www.valvesoftware.com/fi/contact?contact-person=Gabe%20Newell
Are you trolling or just being dumb? Like fr. If you're not going to continue to contribute to the conversation then don't bother talking crap.
I've kept my own cheat undetected for long enough to know how to keep myself from getting 'signature banned' lmao
If you've your own cheat, why using Osiris? hah.
If you've your own cheat, why using Osiris? hah.
Well, I haven't always had my own cheat, hah. It used to be more of a 'test my skills and knowledge' project, so that's why.
... I don't use Osiris anymore, I haven't for a while now. But while I WAS still using it (1 month ago or smth), my main was banned afterwards (about 15 days ago).
I've also had other accounts banned from Osiris, which were strictly for testing Osiris with new stuff, which were also banned, so, yeah.
Really funny, 3 month later and see what happened, nobody believed me, even now, everyone deny it. Anyone who is interested should read these closed issues below.
It is really simple, stop using osiris till it get fixed.
I wasted over 5 accounts with osisris and got vac, my osiris clone was highly modificated.
I use my own injector over 15 years now, never got vac.
Im still using my injector over 3 month now. No vac, no ban, nothing. Just other dll, no osiris anymore ;)
Valve can literally see the source code. What else you can expect? XD
@steel4me Either your Injector is shit or you get game banned and VAC banned afterwards. Every single time someone reports that they received a VAC ban you have to comment and say that nobody believed you. I didn't get VAC banned a single time so stop spreading fake information. Also, we don't know what Injector this guy used. Close this Issue.
@steel4me Either get used to bans or leave hacking. It's so retarded to cry after getting banned for cheats.
oh i missed this useless comments. i don't care about banned accounts. you got me wrong. i just give info. for you, the short version. i used highly modificated teamgamerfood and added lots of things from aimtux or ayyware. Over many, many years, it was no problem to stay undetected. After 4 years i decided to try osiris, changed big parts on my clone, added some things and deleted whole features without vac bypass. i played over 8 month without any detection but always pulled repo and updated osiris. somewhere in february something triggered a vac ban on my accounts. i tried to find out what it was, but nobody was willing to believe. sure thing is. it is not the injector cause im fine since 3 month now and back to my old .dll with less features. but it is okay for me, i don't use osiris anymore ;)
maybe you are just save when you use vac bypass. also vac bypass source is public. imagine the banrate when they sig it.
EDIT: i also really appreciate what daniel provides here, i donated some $ although I no longer use osiris.
It seems to me that it is now undetectable.
It seems to me that it is now undetectable.
No, it isn't 'undetectable', but the hooking is no longer detected.
This issue should be closed.