930bc90c9b6cc5185237a024…
sampleTracked by C2 Tracker · indicators & metadata only, the APK itself is never published
Analyst notes
tcp://192.168.123.151:10086.Recovered configuration
Identification
- SHA-256
- 930bc90c9b6cc5185237a024943e36bbe749461d50f4f3e2348482e27fd819c6
- MD5
- c0addc03956cc74d14bb040a520ddab8
Observed
- Families
- Metasploit
- First seen
- 2026-09-25
C2 configuration (1)
Every indicator extracted from this sample. One row per C2 - each links to its indicator page with Whois, DNS and certificate pivots.
| Indicator | Type | Port | Scheme | Family | First seen |
|---|---|---|---|---|---|
| 192.168.123.151 | ip | 10086 | tcp | Metasploit | 2026-09-25 |
Signing certificate
- Subject CN
- Android Debug
- Issuer CN
- Android Debug
- Fingerprint
- f4c5245ee7a194112441c5ffdab5b377606f203bf49b6428368ae4c9e62d3400
Relationships
Sample → C2 indicators, signing certificate (with every other sample signed by it) and family. Click a node for details, double-click to open its page.
Click a node to inspect it.
About Metasploit
Android payloads generated by Metasploit / msfvenom (meterpreter and command stages), running under the package com.metasploit.stage. The payload dials back to LHOST:LPORT, which is the C2. Two config formats appear in the wild. In the older/plain format the transport URL (tcp://, ssl:// or https://LHOST:LPORT) is a const-string in the DEX. In the newer format the stage carries a protobuf TransportConfig in the static byte array Payload.a, parsed by an embedded protobuf-lite runtime (com.metasploit.a); that array is XOR-masked with a per-build 4-byte key, and because the buffer is zero-padded the leading bytes leak the key, so XORing the array by key[i mod 4] recovers the protobuf and its transport URL. Many samples are red-team or test builds pointing at LAN, loopback or 0.0.0.0 addresses (recorded verbatim); live ones use public IPs or tunnel fronts such as *.lhr.life (localhost.run) and *.loca.lt (localtunnel).