Skip to content

Conversation

@ctkqiang
Copy link

@ctkqiang ctkqiang commented Oct 31, 2025

What this PR does

Adds an auxiliary module that generates QR codes containing Android deep links for security testing. When scanned, these QR codes trigger specific actions in mobile applications, allowing security researchers to test for deep linking vulnerabilities and social engineering scenarios across 5+ popular apps.

Verification Steps

  • Start ./msfconsole
  • use auxiliary/generator/android_deeplink
  • set DEEPLINK_SCHEME weixin:// (or any supported scheme)
  • set DEEPLINK_PATH dl/scanqr?type=qr (or custom path)
  • set FILENAME test_qr.png
  • set SIZE 400
  • run
  • Verify QR code file is generated successfully
  • Verify QR code contains the correct deep link URL
  • Verify scanning the QR code triggers the target app (manual test)

Supporting Information

This module helps test:

  • Deep link handling vulnerabilities in mobile apps
  • Social engineering attack vectors via QR codes
  • App-specific action triggering through custom deep links

Note: This is my first contribution to auxiliary modules, I'm still learning, so please point out any areas for improvement. I understand if this needs more work and appreciate any feedback to help me contribute better and........ please don't kill me.

…e options

- Updated module usage comments for clarity and conciseness
- Integrated a comprehensive list of deep link schemes into DEEPLINK_SCHEME options
- Removed redundant @list_of_deeplink variable after integrating its contents into OptEnum
…e options

- Updated module usage comments for clarity and conciseness
- Integrated a comprehensive list of deep link schemes into DEEPLINK_SCHEME options
- Removed redundant @list_of_deeplink variable after integrating its contents into OptEnum
Create QR codes that trigger app actions when scanned, useful for testing
deep link vulnerabilities and social engineering scenarios across popular apps.
@msutovsky-r7 msutovsky-r7 added the needs-unique-branch The pull request must not be from the master branch label Oct 31, 2025
@github-actions
Copy link

Thanks for your pull request! We require for all contributed code to come from a from a unique branch in your repository before it can be merged.

Please create a new branch in your fork of framework and resubmit this from that branch.

If you are using Git on the command line that may look like:

# Checkout the master branch
git checkout master

# Create a new branch for your feature
git checkout -b <BRANCH_NAME>

# Add your new files
git add modules/my-cool-new-module

# Commit your changes with a relevant message
git commit

# Push your changes to GitHub
git push origin <BRANCH_NAME>

# Now browse to the following URL and create your pull request!
# - https://github.com/rapid7/metasploit-framework/pulls

This helps protect the process, ensure users are aware of commits on the branch being considered for merge, allows for a location for more commits to be offered without mingling with other contributor changes and allows contributors to make progress while a PR is still being reviewed.

Please do resubmit from a unique branch, we greatly value your contribution! 🎉

@github-actions github-actions bot closed this Oct 31, 2025
@ctkqiang
Copy link
Author

OK, will push another one, will see how others are doing with the naming convention.

@ctkqiang
Copy link
Author

Refer: #20668

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-unique-branch The pull request must not be from the master branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants