Privacy + Secure Tech Corner Channel 🛡️
92 subscribers
6.71K photos
588 videos
564 files
16.3K links
Here you can find all about GSI's, ROM's, GKI Kernel's, Tech NEWS, Updates, Root methods, Magisk Module, Overlay's, Hacker things, FLOSS, FOSS, Privacy + Secure Stuff and many more!
Download Telegram
Frida JDWP Loader
This tool dynamically attaches Frida to any debuggable Android process over JDWP, enabling runtime instrumentation without root access.
Perfect for dynamic app analysis, quick pentesting, bug bounty
https://github.com/frankheat/frida-jdwp-loader Video demo: https://x.com/androidmalware2/status/1986022672472359017
Forwarded from Wild Kernels Bot
Wild_KSU_v0.0.217_14016-release.apk
17.4 MB
🔧 CI Manager (TEST BUILD) #ci_3816

📝 style(rectangle mode): reduce vertical spacing and padding inside right-side cards for better visual balance

🔗 Commit: https://github.com/WildKernels/Wild_KSU/commit/f5cfa518f51e036325d66680044b7622c7f86b84
🏃 Workflow: https://github.com/WildKernels/Wild_KSU/actions/runs/19088612551
Wild_KSU_v0.0.217-spoofed_14016-release.apk
17.4 MB
🔧 Spoofed Manager (TEST BUILD) #spoofed_3816

📝 style(rectangle mode): reduce vertical spacing and padding inside right-side cards for better visual balance

🔗 Commit: https://github.com/WildKernels/Wild_KSU/commit/f5cfa518f51e036325d66680044b7622c7f86b84
🏃 Workflow: https://github.com/WildKernels/Wild_KSU/actions/runs/19088612551
Forwarded from TerX Official
🌏 Atmosphere Battery UI ❄️
Released: 11/5/2025
Version: 5.4.5.5-Beta [ Tester ]
Author: TerX Official
Support: Magisk / Apatch / Ksun
Distributed:
@DaveeeJohn

Changelog:
• Added System Cooling
• Added Auto Update
• Added More Faster Than Before
• Added Cache Cleaner in Action Button
• Added System Write over Hardware & Kernel
• Added Auto Balance mode
• Added Surface flinger
• Did not Conflicting any types of modules because of safe write through the hardware
• Fix cache didn't recognize
• Fix Some bugs & Error on line of code
• Fix Watts been Lowered without Overheating



Official Telegram | Here
Creator | TerX
Github | Download
Why is this being released this November? | Click Here
Forwarded from The Hacker News
⚠️ Researchers have found 7 new ways to hack ChatGPT (GPT-4o and GPT-5), including zero-click attacks that can steal chat history and even poison your AI's memory.

OpenAI fixed some of them... but not all of them.

Details here → https://thehackernews.com/2025/11/researchers-find-chatgpt.html
Forwarded from The Hacker News
Google spotted malware that uses Gemini AI to rewrite its own code.

It’s called PROMPTFLUX — a simple script that asks Gemini for new ways to hide from antivirus tools.

More information ↓ https://thehackernews.com/2025/11/google-uncovers-promptflux-malware-that.html
https://github.com/mlm-games/geotag-video-camera

Geotag Video Camera
A simple CameraX + Compose app that overlays a live map and location info on top of the camera preview.

A camera with geo-tag location support

UI tip: Double‑tap anywhere on the preview to open Settings.


Initial context
On first launch, if the app is using MapLibre demo tiles (the default fallback), you’ll see a one‑time notice:

MapLibre demo tiles are for demonstration only since they do not show terrain.
For better maps, use MapTiler or Geoapify and provide your API key.
To configure:

Double‑tap anywhere on the camera preview to open Settings.
Go to Settings → Map.
Pick a provider:
MapTiler: paste your API key in “MapTiler API key”.
Geoapify: paste your API key in “Geoapify API key”.
MapLibre: provide your own style URL if you self‑host tiles; otherwise the app will use demo tiles.
Optionally adjust the map zoom and overlay preferences.
If no key is provided for MapTiler/Geoapify or no custom style URL is set for MapLibre, the app falls back to MapLibre demo tiles.

Highlights
Live overlay: map + coordinates on the camera preview
Works with MapLibre (default), MapTiler, or Geoapify
Compose UI, clean controls; simple mode toggle
Optional debug location for demos

Quickstart
1. Open the app, double‑tap the preview → Settings.
2. Settings → Map: choose a provider.
MapTiler or Geoapify: paste your API key.
MapLibre: use your own style URL, otherwise demo tiles are used.
3. Frame your shot and record.

Permissions
Camera
Location (for GPS overlays and reverse geocoding)
Optional: notifications, audio (for future features)

Notes
Map tiles are fetched from the provider you select.
When using demo tiles, terrain and detail may be limited.
Location data is only embedded locally. No tracking or cloud uploads.
Infinity X 3.4 | A16 QPR0 | TREBLE GSI OFFICIAL-signed

👤 Maintainer: Doze-off
📆 Build Date: 2025-11-05
📝 Security Patch Level: November
⬇️ Download & Changelog
👥 Support


🤝 Join
🔔 Follow

#A16 #Official #TD #GSI #InfinityX #AOSP
I was recently interviewed by Mike Adams on his show, we discussed the integration of Brighteon.AI (https://brighteon.ai) with our phones and laptops.

https://www.brighteon.com/3d7a3a67-2a64-4c7b-843b-1411f9088dbb

Check out this hands on demo of the model on our phone and laptop. This AI knows a TON about herbalism, natural health and survival skills, trained on 100M pages of content.

You can download the model here: https://BrightU.AI/downloads

It will run on local AI clients without an internet connection; It's free, unlimited and downloadable right now.
No deleted account found from 85 scanned users from this group 🚫👻

💬 Send /lang to change language of the bot
Forwarded from krenlol
KernelSU v2.0.0 - Ultra Legacy

- small writeup on what I did to keep support for 3.0 ~ 5.4.

KernelSU moved from prctl to sys_reboot + ioctl for its IPC/API.
This method has to unlock sys_reboot from seccomp so that it is allowed for apps on denylist.
This can allow us to bootstrap and request a file descriptor to use via ioctl.
Basic usage: https://github.com/backslashxx/various_stuff/blob/master/ksu_fd/ksu_fd.c

Now for what I did.
Since we don't have the same seccomp-bpf subsystem as ACK 5.10+
I straight up disable seccomp for allowed apps.

Actually, I'm the one who suggested to use sys_reboot which will also keep a usable syscall for syscall-based communication since we have access to a pointer.

Thats the massive difference, now for small changes.

- /data/system/packages.list trigger
For throne_tracker trigger, we keep LSM hook on inode_rename.
This is way less overhead, way less code and way less maintenance burden.
We also have the asynchronous-ity of throne tracker since ever since, I offloaded throne tracker to a kthread.
Do you really expect me to backport fsnotify handling to 3.0?

- setuid hook
For this we also keep the LSM. same stuff.
This is way less overhead, way less code and way less maintenance burden.

- devpts
we don't hook devpts anymore. you can call pm via 'su -c pm' or su and then pm.

- sys_reboot hook
I went out of my way to meme-out other manual hook ecosystem elites.
so Shirkneko (sukisu) and simonpunk (susfs)
I convinced them to use this signature for sys_reboot hook
ksu_handle_sys_reboot(int magic1, int magic2, unsigned int cmd, void __user **arg);

This way the possibility to extend syscall-based instrumentation is infinite.
Other forks are to follow / following already.
RKSU also picked the same sys_reboot handler signature.
unsure for KSUN.

--
For 5.10+ users, while the driver on my repo will likely compile, I don't assure stability
nor I'll go out of my way to fix if theres issues. Just use upstream. This is not just due to me being lazy about it, this is also respect to upstream.

as always for LKM changes that I like, I just pass it on to kow
so for "LKM+" kind of thing, if you're willing to try bleeding edge stuff, use KowSU.

The commits are properly ordered and commented so if you want to do some integrations yourself
just cherry pick it on your own.

I guess that's it.

have fun.
- xx
Forwarded from Tech & Leaks Zone
Exynos fans resort to editing benchmarks to cope!

Beware of any Exynos 2600 leaks currently, as on twitter, Samsung fans (especially paid reviewers) are glazing results of a chip that doesn't exist. You'll come across the wildest justifications, including die sizes that could match an M4. All of which would be unrealistic for a mobile chip.

The funniest thing? They claim better single performance at lower frequencies than the 9500. With the same, exact, core. Oh, and better IPC too, 10% better, with the same exact core! These, to be true would again reach M4 die sizes just from the sheer cache requirements.

Follow @TechLeaksZone for future PSAs on fake leaks