getifaddrs()ID:
GETIFADDRS_VPNCategory: Interfaces Status in RKNHardering 2.10.0: Active check Role in the verdict: High
This page describes the actual implementation in RKNHardering 2.10.0. It distinguishes what can be done without root, what requires root, and where a mitigation only reduces one signal without hiding the VPN as a whole.
detectGetifaddrsVpn() calls libc getifaddrs() and searches for the exact names tun0, tun1, utun0, wg0, ppp0, and xfrm0. Repeated address records are not deduplicated, so the same name may appear multiple times in the detail.
The ifaddrs chain contains at least one entry with one of the six exact names; the UP state is not checked.
The direct userspace interface list contains a typical VPN-like name. Unlike the main interface-enumeration check, this deep vector can trigger even when the interface does not have the UP flag.
How the line affects the report: The line sets detected=true and is treated as a high-confidence local indicator.
This is not the project’s complete matcher: it does not search for tailscale0, svpn0, zt*, gre*, renamed interfaces, or OEM-specific interfaces. A userspace inline hook can replace getifaddrs() results, but raw netlink and other paths remain separate checks.
This line must be evaluated together with neighboring signals. A clean result from a single API does not simultaneously cover Java Binder, libc, raw netlink/syscalls, procfs/sysfs, local sockets, and server-side indicators.
The most reliable non-root approach is not to create a VPN interface on the phone being tested: move the tunnel to a router, travel router, separate gateway phone, or another network node. Per-app bypass in VpnService changes the route used by the selected app, but establish() still creates a system VPN interface, so local interface checks may continue to trigger. A local HTTP/SOCKS proxy mode without TUN can sometimes remove this specific vector, but it leaves listening ports and proxy settings and does not cover apps that ignore the proxy. Without root, one app cannot filter the getifaddrs() result seen by another app. A rootless hook or repacked target APK creates more obvious integrity indicators and is not recommended.
Laboratory-grade hiding usually requires a system Java layer and one native backend. With VPNHide, this means the APK plus Vector/LSPosed scoped only to System Framework, and exactly one of kmod, KPM, or Zygisk. For a check that may use a direct syscall or netlink, kmod/KPM is preferable: a userspace Zygisk hook can be bypassed and leaves traces inside the process. Review the VPNHide coverage map first, and download builds only from the official release page. VPNHide Next claims broader coverage, but also warns about possible boot loops and kernel panics; it should be tested only on a test device. Zygisk can intercept the libc call, but raw syscalls and netlink bypass userspace interposition. A kernel backend combined with a system_server layer is preferable for a consistent result.
adb shell ip -br link
adb shell 'cat /proc/net/dev | grep -E "tun0|tun1|utun0|wg0|ppp0|xfrm0"'
Exact reproduction requires a small native harness using getifaddrs(); ip uses its own netlink paths and serves only as a comparison.
After any change, force-stop both RKNHardering and the VPN client, start them again, and repeat the full scan. Zygisk, Xposed, and kernel modules usually require a reboot. Compare not only this line but also neighboring signals: a partial hook often creates inconsistencies between APIs.
The probe itself runs with ordinary app permissions and does not request root. The ADB commands below are for orientation only: adb shell runs under a different UID and may see either more or less than the app process. The decisive test is to run the check again after a force-stop.
An incomplete userspace hook creates discrepancies with RTM_GETLINK, ifindex lookups, and Java APIs; this strengthens trim-oracle and mismatch signals.
Revert the most recent change: disable the added module or rule through its normal manager, reboot the device, and repeat the baseline scan. Do not layer another hook on top of an unknown state.
High. Verified against the exact-name loop in detectGetifaddrsVpn(); the kind is high confidence.
The status of a third-party solution does not automatically carry over to this device. A module developer’s claim is only the initial hypothesis; confirmation requires a reproducible RKNHardering result on the specific Android version, firmware, and kernel.
native_signs_probe.cpp — native probe implementation.VpnNativeDetectorChecker.kt — deep VPN verdict and confidence.NativeSignalId.kt — complete ID registry.NativeSignalCatalog.kt — category, slug, and line mapping.Related signals: interface-enumeration, rtm-getlink-vpn, trim-oracle, sysclassnet-vpn.