Jump to content

Hacker in my server

paulinhoajr
 Share

Recommended Posts

paulinhoajr Newbie

paulinhoajr

Posted
  • Author
Posted

Looks from time 01:23:31

  Reveal hidden contents

 

Link to comment
Share on other sites
JasonTM Newbie

JasonTM

Posted
Posted

I would also add keyword exec to scripts.txt. You can set it to 1 and run your server. Then add exceptions for all of the stuff running on your server. Then set it to a 5.

You can start with this 

1 exec !"execVM \"\z\addons\dayz_code" !"execVM \"ca\modules\functions\systems" !"progress_monitor = [] execVM \"DZE_Hotfix_1.0.6.1A\system\progress_monitor.sqf\";" !"_scr = _this execVM '\ca\Data\ParticleEffects\SCRIPTS\init.sqf';"

 

 

Link to comment
Share on other sites
BigEgg Newbie

BigEgg

Posted
Posted

There is actually a much easier way to block this from happening.

 

In z\addons\dayz_server\compile\server_deleteObj.sqf:

 

Find: 

//remove from database

 

Place this above it: 

if !(isPlayer _activatingPlayer) exitWith {diag_log format["Attempted hacker attack cancelled! Called by: %1", _activatingPlayer];};

 

It will stop that hack from happening :)

Link to comment
Share on other sites
paulinhoajr Newbie

paulinhoajr

Posted
  • Author
Posted

I did that,

now :

01.07.2017 18:14:54: CARRASCO (189.4.74.56:24790) 982344dae0f153a8012c72380ae2d2a5 - #0 "PVAHR_0_r8o0e1u5u3g245a7x53" = ["CARRASCO","76561198119665789","SLOG_NP",[78,101,119,32,80,108,97,121,101,114,58,32,91,34,51,48,51,54,34,44,91,93,44,91,93,44,91,48,44,48,44,48,93,44,116,114,117,101,44,34,68,97,121,90,32,69,112,111,99,104,32,49,46,48,46,54,46,49,34,44,34,83,117,114,118,105,118,111,114,50,95,68,90,34,44,116,114,117,101,44,116,114,117,101,44,48,44,91,93,44,48,44,48,44,53,48,48,48,93]]

 

Link to comment
Share on other sites
BigEgg Newbie

BigEgg

Posted
Posted
  On 7/1/2017 at 9:49 PM, DuMa said:

 

That won't stop it if the hacker uses


**** EDITED ****

They can frame someone else innocent as well xD.

Expand  

Thanks for posting the solution dumbass :) If you didn't think I knew that, then you need to do a reality check. Hackers aren't that smart and were using public scripts. Great job man

Link to comment
Share on other sites
BigEgg Newbie

BigEgg

Posted
Posted
  On 7/1/2017 at 11:11 PM, DuMa said:

Lol. Actually I have a better solution which DCloud Antihack uses that is to check the position of the Activating player to the position of the object. If its less than X meters depending on the situation the function continues else it logs the Base Wipe into the RPT.

Expand  

Okay? You are completely missing the point. You just posted a frame solution on a public forum. Nice job.

Link to comment
Share on other sites
BigEgg Newbie

BigEgg

Posted
Posted
  On 7/1/2017 at 11:20 PM, DuMa said:

As far as I know the people behind this doesn't have the ability to use the solution I posted. They don't know what they are doing. So I think I did the right thing hehe. And I posted another solution which is to check the distance. Noone is smart enough to fake that unless they wanna get banned by Infistar for 4000+ teleports within 5 seconds.

Expand  

Then you know very little because they do have the capability (obviously, as they were using it on this guy's server). Grats though, I look forward to the release of DCloud, as I am sure it will stop it ;)

Link to comment
Share on other sites
paulinhoajr Newbie

paulinhoajr

Posted
  • Author
Posted
  On 7/1/2017 at 6:00 PM, BigEgg said:

There is actually a much easier way to block this from happening.

 

In z\addons\dayz_server\compile\server_deleteObj.sqf:

 

Find: 

//remove from database

 

Place this above it: 

if !(isPlayer _activatingPlayer) exitWith {diag_log format["Attempted hacker attack cancelled! Called by: %1", _activatingPlayer];};

 

It will stop that hack from happening :)

Expand  

 

I found a problem here, dead players are born with same body. So I removed it.

Link to comment
Share on other sites
paulinhoajr Newbie

paulinhoajr

Posted
  • Author
Posted

If you can help me, thank you.

This kick:

04.07.2017 18:22:32: Fee (177.189.231.108:2304) b3531b4bc8f8165663c2e7cf97b6b557 - # 7 "" _2 "," _ 1 "," _ b "," _ idc_arr "," _ extra_kills "," _ tally_kills "," _ full_box_count " "_partial_box_tally", "_ add_kills"];

_kills = _this se"

I already tried everything but it does not work

  Reveal hidden contents

 

Link to comment
Share on other sites
Anhor Newbie

Anhor

Posted
Posted

Delete your _box line in your scripts.txt and add this one: 

5 "_box" !="{show_loot_infiSTAR = !show_loot_infiSTAR;};\n};\nif(isNil \"show_boxes_infiSTAR\")then{show_boxes_infiSTAR = false;};\nfnc_BoxS = {\n" !="_full_box_count" !="_partial_box_tally"

A short question ....... you´re sure you running Epoch 1.0.5.1? Your infiSTAR looks like the one for 1.0.6.1

If so, this thread is in the wrong category.

 

Link to comment
Share on other sites
  • 4 weeks later...
_Lance_ Newbie

_Lance_

Posted
Posted
  On 7/1/2017 at 10:02 PM, DuMa said:

 

01.07.2017 18:14:54: CARRASCO (189.4.74.56:24790) 982344dae0f153a8012c72380ae2d2a5 - #0 "PVAHR_0_r8o0e1u5u3g245a7x53" = ["CARRASCO","76561198119665789","SLOG_NP",[New Player: ["3036",[],[],[0,0,0],true,"DayZ Epoch 1.0.6.1","Survivor2_DZ",true,true,0,[],0,0,5000]]]

 

Thats the meaning of it. Thats only a log why kick for that?(Infistar)

 

That is triggered by these lines in Infistar AH.sqf about line 4597. 

	[] spawn {
		waitUntil {uiSleep 1;!isNil 'PVCDZ_plr_Login'};
		waitUntil {uiSleep 1;str PVCDZ_plr_Login != '[]'};
		if(PVCDZ_plr_Login select 8)then
		{
			_log = format['New Player: %1',PVCDZ_plr_Login];
			_name = 'DEAD';if((alive player)&&(getPlayerUID player != ''))then{_name = name player;};
			[_name,getPlayerUID player,'SLOG_NP',toArray (_log)] call "+_randvar364637+";
		};
	};

 

And this is a new player log. Add an exception for that in BE Filters. 

Expand  

 

Sorry to rehash a month old thread but I started getting this kick about a week ago and I'm weak at making exceptions for complicated kicks. Wondering if you or anyone reading this can help make a filter for this issue. Doesn't seem to happen to all players, but some players on first login get a kick and I get this in the publicvariable log:

#0 "PVAHR_0_k9f9c3d75554d7d1536" = ["<PLAYER_NAME_HERE>","<PLAYER_ID_HERE>","SLOG_NP",[78,101,119,32,80,108,97,121,101,114,58,32,91,34,53,52,50,51,34,44,91,93,44,91,93,44,91,48,44,48,44,48,93,44,116,114,117,101,44,34,68,97,121,90,32,69,112,111,99,104,32,49,46,48,46,54,46,49,34,44,34,83,117,114,118,105,118,111,114,50,95,68,90,34,44,116,114,117,101,44,116,114,117,101,44,48,44,91,93,44,53,48,48,48,48,48,44,48,44,48,93]]

For anyone who got booted a 2nd time the quick fix was: !="PVAHR_0_k9f9c3d75554d7d1536" but the variable is different for each player so every time this happens I'd have to add an exception for that user's kick. I considered trying !="SLOG_NP" but haven't tested if that will fix the kick yet, but I'm afraid it's going to be a trickier exception than that... Not sure why infistar is even kicking for this anyway. - Any advice is greatly appreciated, thanks! - ALso I wanted to post this in the BE FILTERS HELP thread which I could have sworn I have seen in this forum before but was unable to find it, so linked it here.

 

 

Link to comment
Share on other sites
LunatikCH Newbie

LunatikCH

Posted
Posted
  On 8/2/2017 at 11:21 PM, _Lance_ said:

 

Sorry to rehash a month old thread but I started getting this kick about a week ago and I'm weak at making exceptions for complicated kicks. Wondering if you or anyone reading this can help make a filter for this issue. Doesn't seem to happen to all players, but some players on first login get a kick and I get this in the publicvariable log:

#0 "PVAHR_0_k9f9c3d75554d7d1536" = ["<PLAYER_NAME_HERE>","<PLAYER_ID_HERE>","SLOG_NP",[78,101,119,32,80,108,97,121,101,114,58,32,91,34,53,52,50,51,34,44,91,93,44,91,93,44,91,48,44,48,44,48,93,44,116,114,117,101,44,34,68,97,121,90,32,69,112,111,99,104,32,49,46,48,46,54,46,49,34,44,34,83,117,114,118,105,118,111,114,50,95,68,90,34,44,116,114,117,101,44,116,114,117,101,44,48,44,91,93,44,53,48,48,48,48,48,44,48,44,48,93]]

For anyone who got booted a 2nd time the quick fix was: !="PVAHR_0_k9f9c3d75554d7d1536" but the variable is different for each player so every time this happens I'd have to add an exception for that user's kick. I considered trying !="SLOG_NP" but haven't tested if that will fix the kick yet, but I'm afraid it's going to be a trickier exception than that... Not sure why infistar is even kicking for this anyway. - Any advice is greatly appreciated, thanks! - ALso I wanted to post this in the BE FILTERS HELP thread which I could have sworn I have seen in this forum before but was unable to find it, so linked it here.

 

 

Expand  

This

!"SLOG_NP"

without the '=' because the '=' means the whole kick log must be exactly the same as the exception the "SLOG_NP" just means anything containing SLOG_NP even when its FRGTDHRHSLOG_NPEGEHTE it wont kick you.

Link to comment
Share on other sites
_Lance_ Newbie

_Lance_

Posted
Posted
  On 8/3/2017 at 4:18 AM, LunatikCH said:

This

!"SLOG_NP"

without the '=' because the '=' means the whole kick log must be exactly the same as the exception the "SLOG_NP" just means anything containing SLOG_NP even when its FRGTDHRHSLOG_NPEGEHTE it wont kick you.

Expand  

Amazed it did turn out to be short and sweet - thank you very much!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing

  • Discord

×
×
  • Create New...