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.

Sign up for GitHub

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

Jump to bottom

Bad requests #8

Open
gongtaoo opened this issue Dec 22, 2024 · 1 comment
Open

Bad requests #8

gongtaoo opened this issue Dec 22, 2024 · 1 comment

Comments

@gongtaoo
Copy link

Has anything changed? I have everything setup, and currently have the payload running, but am getting a bunch of HTTP 400s from the MS graph endpoint.

image

image
@gongtaoo
Copy link
Author

gongtaoo commented Dec 22, 2024 •
edited
Loading

I realized I didn't load the gs cna. But after loading the graphstrike cna, the raw shellcode that gets generated and loaded with my custom loader, crashes the process. I don't see the process running. And if you look at the screenshot from above, it doesn't seem like the beacon is actually making the requests using all of the indicators defined in the hooked http functions in graphldr. It's making requests based off of whatever indicators is in the malleable profile. I've tried loading the shellcode with several different loaders, and no beacon gets created. I am also using the latest version of CS, if that makes a difference. Am I missing anything?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gongtaoo