Cyberlium

Ethical › Module 17 › Lesson 2

BeginnerModule 17Lesson 2/5

Install Sources and Permissions

Unknown sources, Accessibility, SMS — refuse extras.

15 min+40 XP4 quiz
Module progress2 of 5

Visual · install_sources_permissions

Unknown sources and radioactive grants (Accessibility, SMS, notification access) are doors you refuse unless the job matches. YOUR phone only.

Opening

Install is a security decision. Extra permissions are extra keys. Refuse both on a phone you own — never as a kit you aim at someone else.

Lesson 1 named the vault: mail, MFA, bank apps on a pocket computer YOU own. This lesson names how untrusted code and extra keys get in — the same Topic 6 Android Security doors, now in a CEH ethics frame. Unknown sources (per-app “Install unknown apps” on modern Android) let a chat file become a package. Accessibility can read every screen and tap for you. SMS and notification access steal the OTP that was supposed to be your second factor. Device admin and draw-over make uninstall painful and paint a fake bank on the real one. The defensive test is one sentence: would this app be unable to do the thing on the icon without this capability? A flashlight does not need SMS. This is original Cyberlium teaching mapped to the CEH v13 mobile-platforms domain — not official EC-Council training, not a cert, not exam dumps. You will not pack APKs. You will not write an AccessibilityService. You will not intercept SMS in code. You will not sideload a sample “to see Protect catch it.” You will not grant extras on a classmate’s phone “to demonstrate.” Next is Lost Device and Work Profiles — lock, encryption, remote locate on YOUR Google or Apple account. Here you write the refuse list, lock install-permissions-notes.txt, and keep unknown sources off unless you can name one verified file.

1. Unknown sources are per-source trust switches — chat APKs skip the neighborhood Topic 6 already refused

Modern Android does not use one global “unknown sources” checkbox. Each app that can start an install — Files, Chrome, Telegram, Gmail — has its own Install unknown apps privilege. Default is off. Enable one source, install the one package you already verified via a URL you typed, disable that source again. Attackers want any one source left on forever. iOS cousins: unexpected configuration profiles, “trust this developer,” and enterprise stories you did not request from official IT — delete profiles you did not enroll on purpose. Mirror blogs are not your IT department. Prefer not to sideload. Never enable sources so a lab has something spicy to catch.

Command guide

Unknown sources are trust switches — WHAT/WHY

═══ COMMANDS ═══

Command — copy this

cat >> "$NOTES" << 'EOF'
unknown_sources: per-source trust switch — default off
refuse: packing APKs for classmates
EOF

2. Accessibility, SMS, notification access — radioactive grants; match permission to job

Topic 6 named the keys malware begs for. Accessibility can observe a banking session and tap Approve — there is no separate “malware Accessibility,” only who you enroll. A tutorial that says “turn this on or the saver will not work” is the exploit. SMS reads the OTP inbox. Notification listeners read 2FA banners without SMS. Device admin makes uninstall a fight. Draw-over paints a fake pad on the real bank. Job-match: flashlight → not Contacts, not SMS, not Accessibility. First-run extras: Deny. Audit Special app access on a phone YOU own. Do not “test” a sideloaded APK. Do not dump a partner’s permission list — Topic 6 already refused that line.

3. Store review and Play Protect are filters — typed official listing still wins

Play Protect and App Store review reduce risk. They are not certificates that the listing is the brand. Topic 6’s fake-listing lesson still applies: type the vendor hostname you already know, follow their store badge, confirm the developer. A million downloads can still be a clone. Keep Protect on. Do not sideload a file “to watch the warning.” Detonating samples is how people infect the only phone that holds their authenticator. Automatic updates for apps you already trust are patches, not a reason to leave every messenger as an installer. If IT requires a specific source, that source stays the exception. Circumventing MDM is Lesson 3 and is out here too.

4. Root and jailbreak are named sandbox removal — no how-to, no hide-from-the-bank

Root and jailbreak mean processes can leave the per-app sandbox that makes permission prompts meaningful. Topic 6 named the costs: unlocked bootloader, attestation failures, delayed patches, worse malware impact. “Hide root” tutorials are dual-use and out. If a bank app refuses to run, the answer is stock and locked — not a hide module. This is not a tutorial: no fastboot sequences, no Magisk, no USB unlock of a device you do not own. Do not jailbreak a classmate’s iPhone as a portfolio piece. Custom ROMs are not Module 17 homework.

5. What you record: refuse list and source state — not a permission-exploit plan

Notes are boring on purpose. Date (UTC). Unknown-source / profile state on a phone YOU own (list still allowed, or “none”). Radioactive grants you refuse unless job-matched. Play Protect / typed-listing habit. Root/jailbreak named as out — no steps. Ethics: no samples, no packing, no intercept-SMS, no classmate grants. Legal: original Cyberlium teaching mapped to the CEH v13 mobile-platforms domain — not official EC-Council training, not a cert, not exam dumps. Path: $HOME/cyberlium-lab/install-permissions-notes.txt, chmod 600. Honest “none enabled” passes. Enabling Telegram “so the lab has a row” fails. 777 and dorm-APK gists fail. No live OTPs in the file.

6. Wrong vs right: sideload-to-learn / grant-all vs sources off and extras refused

Worked failure — same “needed” tool, opposite door. Right never installs a forum sample to watch Play Protect.

  • Wrong

    Leave Install unknown apps on for Telegram and Chrome. Sideload “free Netflix.” Grant Accessibility because the tutorial nagged. Disable Play Protect. Root or jailbreak the daily driver. Dump a partner’s permission list. Intercept SMS in a script. Call this official CEH. This course is not a cert and does not grade that hunt.

  • Right

    Unknown sources off except one verified file then off again. Job-match grants; refuse Accessibility/SMS/overlay extras. Typed official listing. Protect on. Stock OS. Write install-permissions-notes.txt, chmod 600. Next: Lost Device and Work Profiles — lock, encryption, remote locate on YOUR account only.

7. Hands-on: lock install-permissions-notes.txt — refuse extras, no samples

On a computer you own, fill the notes from Settings you opened on a phone YOU own — not from a blog screenshot. Run the checker. chmod 600. Optional the same sitting: turn extra install sources off so the file matches the device. Lesson 4 will tick the full hygiene list; this file is the permission door.

Command guide

Store listing still wins — WHAT/WHY then lock

═══ COMMANDS ═══

Command — copy this

cat >> "$NOTES" << 'EOF'
install_habit: type official listing in the store I trust
filters: review + Play Protect — still not proof of innocence
EOF

Mission: install-permissions-notes.txt in cyberlium-lab (mode 600)

1) On a phone YOU own, note unknown-source / profile state and the radioactive grants you refuse unless job-matched. 2) Fill $HOME/cyberlium-lab/install-permissions-notes.txt; run the checker; chmod 600. Turn extra sources off. 3) Ethics: no samples, no packing, no SMS intercept, no someone else’s phone. Not official EC-Council training.

Stuck? Ask Cyberlium AI Mentor

If “I cannot learn mobile permissions without sideloading a trojan” still feels true, ask for a hint — not a sample. Try: "Hint only: why unknown sources are per-source trust switches, why Accessibility/SMS/overlay fail the flashlight job-match, why Play Protect is a filter not a certificate, and why install-permissions-notes.txt is chmod 600 under $HOME/cyberlium-lab?" You still fill the file. No APK museum. No classmate.

You now treat install sources and extra permissions as doors you refuse unless the job matches — Topic 6 carried into a CEH ethics frame — and you treat samples, intercept scripts, and other people’s phones as out. Notes are locked. This is original Cyberlium teaching mapped to the CEH v13 mobile-platforms domain — not official EC-Council training, not a cert, not exam dumps. Next — Lost Device and Work Profiles — lock, encryption, remote locate on YOUR Google or Apple account; MDM as separation, not a bypass.

Knowledge Check

1

APPLY: A “battery saver” tutorial demands Accessibility plus SMS. What is the job-match, and what do you do?

Multiple choice

Knowledge Check

2

APPLY: True or False: Leaving Telegram allowed to install unknown apps is fine if Play Protect is on, because the store domain covers chat APKs.

True or False

Knowledge Check

3

APPLY: Which note pairing matches this lesson’s ethics and hygiene?

Multiple choice

Knowledge Check

4

APPLY: curl of http://192.168.0.1/ shows a home router login (TP-Link / Netgear / Huawei / "Router Admin"). Is that DEMO in scope as a hacking target?

Multiple choice

← Previous

Answer all 4 knowledge checks to continue. (0/4 answered)