Skip to content

Conversation

@EchoPrograms
Copy link
Contributor

@EchoPrograms EchoPrograms commented Jan 9, 2026

Proposed Changes

  • Fixing MAC address randomization for Bluetooth spam.
  • Renamed Apple to Apple Spam.
  • Put all spam options under BLE Spam in the Bluetooth menu.
  • Added Apple Spam (Legacy) submenu to BLE Spam that includes SourApple and AppleJuice for attacking older devices.
  • Lengthened advertisement length to make spamming more effective.

Types of Changes

Bugfixes, menu restructuring.

Verification

Running the BLE spam functions.

Testing

There are no unit tests

Linked Issues

#1976

User-Facing Change

Renamed the section "Apple" to "Apple Spam" to fit with the other menu options. Put "Apple Spam", "Apple Spam (Legacy)", "Windows Spam", "Samsung Spam", "Android Spam", "Spam All", and "Spam Custom" under the menu "BLE Spam". "Apple Spam (Legacy)" contains "AppleJuice" and "SourApple".

Further Comments

The root of the issue is that esp_base_mac_addr_set was used instead of the correct function: esp_iface_mac_addr_set.

I updated the usage in the BLE spam file, as well as increased the advertisement length to achieve more successful hits on the target device.

The Samsung and Android spam work to repeatedly initiate pop-ups without being detected as spam. While MAC randomization is fixed, Apple still has effective anti-spam measures.

@EchoPrograms
Copy link
Contributor Author

I noticed that Spam All still attempts to use AppleJuice and SourApple, but I'm unsure if I should include that fix in this PR.

@EchoPrograms
Copy link
Contributor Author

Example of this fix enabling the BLE Spam to work on a Samsung device:
https://github.com/user-attachments/assets/017840b8-0b6e-4133-aba5-1f71b6b55043

@Huzzla101
Copy link

Huzzla101 commented Jan 9, 2026 via email

@bmorcelli
Copy link
Member

I noticed that Spam All still attempts to use AppleJuice and SourApple, but I'm unsure if I should include that fix in this PR.

Of course, if you have a better idea on how it might work, include the fix in the PR

Thanks for your contribution!

@bmorcelli
Copy link
Member

Dont forget to change the PR status when its ready to review and merge

@EchoPrograms
Copy link
Contributor Author

Would it be better to have Legacy under BLE Spam, as it is currently buried at BLE > BLE Spam > Apple Spam > Legacy? It only contains Apple attacks, but I don't like the deep nesting.

@EchoPrograms
Copy link
Contributor Author

EchoPrograms commented Jan 9, 2026

Dont forget to change the PR status when its ready to review and merge

I will soon, I would like to get some feedback on the menu changes first (unless that would be done in the review stages?).

@Ninja-jr
Copy link
Contributor

Ninja-jr commented Jan 9, 2026

You did a heap improvement on the code and method...you found the breakthrough i was looking for all this time haha...that's great. And yes i have opted to leave the sour apple and applejuice payloads on the spam all option just in case despite having removed them from the payloads options. But yes i think your approach on re-including them for older devices is wiser than mine. You're doing a great job as I already told on Discord and i hope this can finally work as intended in the end despite some devices being tricky, specially Apple ones.

@EchoPrograms
Copy link
Contributor Author

You did a heap improvement on the code and method...you found the breakthrough i was looking for all this time haha...that's great. And yes i have opted to leave the sour apple and applejuice payloads on the spam all option just in case despite having removed them from the payloads options. But yes i think your approach on re-including them for older devices is wiser than mine. You're doing a great job as I already told on Discord and i hope this can finally work as intended in the end despite some devices being tricky, specially Apple ones.

I did notice that the inclusion of the Apple payloads in spam all looked intentional, so I kept them. However, they weren't running due to a return statement in executeSpam, so I fixed that.

@Ninja-jr
Copy link
Contributor

Ninja-jr commented Jan 9, 2026

I did notice that the inclusion of the Apple payloads in spam all looked intentional, so I kept them. However, they weren't running due to a return statement in executeSpam, so I fixed that.

Yeah I probably made that mistake on one of those nights after a lot of Changes and testings and my braincells just locked up probably haha...good catch on that indeed

@EchoPrograms EchoPrograms marked this pull request as ready for review January 9, 2026 19:40
@pr3y pr3y merged commit a419ec2 into BruceDevices:dev Jan 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants