Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Argument #94

Closed
MyraBaba opened this issue Oct 28, 2024 · 13 comments
Closed

Invalid Argument #94

MyraBaba opened this issue Oct 28, 2024 · 13 comments
Labels
question Further information is requested

Comments

@MyraBaba
Copy link

python .\zircolite.py --evtx .\7\ --rules C:\PURE7\rules.json

Traceback (most recent call last):
File "C:\RE7\Zircolite\zircolite.py", line 2713, in
main()
File "C:\RE7\Zircolite\zircolite.py", line 2622, in main
zircoliteCore.run(LogJSONList, saveToFile=args.keepflat, args_config=args)
File "C:\RE7\Zircolite\zircolite.py", line 1227, in run
flattener.runAll(EVTXJSONList)
File "C:\RE7\Zircolite\zircolite.py", line 830, in runAll
results = self.run(evtxJSON)
File "C:\RE7\Zircolite\zircolite.py", line 777, in run
with open(str(file), "r", encoding="utf-8") as JSONFile:
OSError: [Errno 22] Invalid argument: 'tmp-6W5YO034\ID400-800-CrackMapExec payload execution.evtx-R0YQ824M.json'

@wagga40
Copy link
Owner

wagga40 commented Oct 28, 2024

This is typically the error that appears when the AV trigger on the temp files. I recommend you to add Zircolite directory to AV exclusions.
Did you check, your AV logs ?

@wagga40 wagga40 added the question Further information is requested label Oct 29, 2024
@MyraBaba
Copy link
Author

MyraBaba commented Oct 30, 2024

@wagga40

Hi I have good case for you. rules.json and evtx files. hayabusa took 390 sec zircolite took 1400sec.

I can share the data privately if you want to examine.

Best

PS: if you put elapsed time for each event result in screen printing good for debug

@wagga40
Copy link
Owner

wagga40 commented Oct 30, 2024

I can share the data privately if you want to examine.

yeah I’m interested, how do you want to proceed ?

@MyraBaba
Copy link
Author

give me your email pls

@MyraBaba
Copy link
Author

@wagga40

I can send links for rules and evtx zip for test to your email.

As far as I see its take too long for some queries.

ie: 17.000 result.. takes too long to query.

hayabusa always around 4 min - 5 min.

Screen Shot 2024-10-31 at 16 28 22 Screen Shot 2024-10-31 at 16 23 41

@MyraBaba
Copy link
Author

@wagga40

more diagnosis clues:

same log and same json rules:

on my vmware windows 10 took 297 sconds

on another server ; vmware win server 2019 took 14500 seconds. !

both machine hayabusa 300 seconds

@wagga40
Copy link
Owner

wagga40 commented Oct 31, 2024

email : seringues-06.phyla@icloud.com

did you try with the v3 version in the dev branch ? https://github.com/wagga40/Zircolite/tree/v3.0 (very unstable, csv output not working)

Sometimes memory is quite the bottleneck and the rulesets have to be tailored because somes rules are very noisy and take long time to execute.

@MyraBaba
Copy link
Author

MyraBaba commented Oct 31, 2024 via email

@wagga40
Copy link
Owner

wagga40 commented Oct 31, 2024

You should use zircolite_dev.py

Normally it should work only with this file

@MyraBaba
Copy link
Author

MyraBaba commented Nov 1, 2024 via email

@wagga40
Copy link
Owner

wagga40 commented Nov 1, 2024

I sent you an email address in a previous answer, could you share your samples ?

@wagga40
Copy link
Owner

wagga40 commented Nov 1, 2024

Whith the news version (https://github.com/wagga40/Zircolite/tree/v3.0) of Zircolite and default ruleset or your ruleset, it took 23 sec.

RAM and Storage speed (SSD vs non SSD) can change the results.

Example

@wagga40
Copy link
Owner

wagga40 commented Nov 1, 2024

I've tested in a Windows VM. It took 44 sec

@wagga40 wagga40 closed this as completed Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants