AUTHORIZED ARTIFACTS ONLY

Unified queue

Connecting

NEW ANALYSIS

Turn a package into one reverse-engineering and Firebase packet.

Static analysis only. The artifact is never executed, and external checks stay off unless you enable them.

AUTOMATED PIPELINE

  1. 01
    Identify & containHashes, type, archive-bomb and traversal checks
  2. 02
    Android intelligenceManifest, SDKs, components, signing fingerprints
  3. 03
    Code & configurationAPKRecon, JADX, endpoints and redacted secrets
  4. 04
    Cloud postureFirebase and storage indicators; live reads only when opted in

WORKSPACE

All queued work

Unlock the workspace to load jobs.

AWS S3 + DIGITALOCEAN SPACES

Read-only posture audit

Credentials are held in a one-use memory lease and are never written to the queue. No object body is downloaded. Every mutating S3 operation is blocked in code.

Audits run in the same managed queue as artifact and Firebase analysis. Results appear in Unified queue.

FIREBASE + GOOGLE CLOUD

Service-account blast-radius audit

Authenticate one company-owned service account and enumerate only bounded, read-only metadata. The credential is consumed from memory and is never saved in the job.

Read-only enumeration includes aggregate Firebase Auth counts, shallow RTDB key counts, Firestore database/collection counts, Storage metadata counts, IAM service-account counts, and testIamPermissions. No user identifiers, database values, collection names, object names, access tokens, or private keys are written to reports.

SAFETY BOUNDARY

One credential, one queued run

GETUsers, RTDB instance metadata, Firestore databases, Storage metadata, IAM identities
Metadata POSTFirestore listCollectionIds and Cloud Resource Manager testIamPermissions only
BlockedUser changes, database writes, document reads, uploads, downloads, deletes, function calls, proxying

ADMINISTRATION

Workspace management

Create isolated teams, rotate scoped access keys, and disable access without deleting reports.

NEW WORKSPACE

Create an isolated workspace

A scoped key is generated once. Jobs and reports are stored in a separate private directory.

ACCESS KEY

One-time key delivery

Create a workspace or rotate a key to receive a new scoped key.

ACCESS BOUNDARIES

All workspaces

Administrator access is required.

AUDIT TRAIL

Recent changes

No workspace changes recorded.

OPERATOR PLAYBOOK

From artifact to actionable report

1

Submit

Upload only an application or archive you own or are authorized to assess. HarborData stores it in a private per-job directory with mode 0600.

2

Contain

Before extraction, the pipeline blocks absolute paths, parent traversal, oversized entries, excessive entry counts, and expansion bombs.

3

Map the app

Androguard maps package metadata, permissions, exported Android components, SDK targets and certificate fingerprints. APKRecon extracts high-signal configuration and credential candidates without showing raw values.

4

Recover source

JADX creates navigable Java/Kotlin-like source and resources. Split packages are unpacked and handled as one job. Native libraries are inventoried separately.

5

Review cloud signals

Firebase project IDs, service-account identities, S3 buckets, Spaces endpoints, domains and URLs are correlated into the report. Discovered credentials stay fingerprint-only unless the separate authorized posture-audit option is enabled.

6

Validate carefully

Network checks are opt-in, rate-limited and read-only. Use the Firebase SA screen for a separately supplied credential, or explicitly enable the discovered-SA option for an owned artifact; writes, deletes and object-body downloads remain blocked.

FIREBASE ASSESSMENT

Safe automation and manual review boundaries

Live-safe automation is capped, rate-limited, and read-only. Authenticated checks require a separate credential option, server policy and ownership confirmation. Manual-only or destructive checks are never automated by HarborData: no account creation or deletion, password-reset emails, database writes, uploads, callable function invocation, or exploit payloads.

Live-safe automation Manual only / destructive
Live-safe automation

Recon

Correlate project IDs, app IDs, API hosts, buckets, database URLs, functions, hosting, and client configuration found in the artifact or public metadata.

Manual only

Auth configuration

Review enabled providers, anonymous access, user-enumeration behavior, password policy, MFA, and tenant settings in an authorized console. Account actions and password-reset flows are out of scope.

Live-safe automation

RTDB

Use bounded unauthenticated GET requests against discovered Realtime Database roots. Rules validation that requires writes, payloads, or credentials is manual only.

Live-safe automation

Firestore

Perform capped public read and metadata checks only. Collection guessing, document writes, deletes, and rules testing with exploit payloads remain manual only.

Live-safe automation

Storage

Check discovered bucket and object exposure with bounded metadata or HEAD requests. Object uploads, deletes, overwrites, and body downloads are not automated.

Live-safe automation

Remote Config

Inspect client defaults and make bounded public read checks where applicable. Publishing, activating, or changing templates is manual and destructive.

Static inventory / manual review

Functions / Hosting

Discovered Functions and Hosting endpoints are inventoried only. Function invocation is never automated—not with GET, HEAD, POST, callable requests, fuzzing, or exploit payloads.

Manual only

authorizedDomains / FDL

Review authorized domains and Firebase Dynamic Links configuration in the owned project console. Redirect or domain-takeover validation requires a separately controlled manual plan.

Explicit authorized run

IAM / service-account identity

Artifact scans fingerprint discovered key material without using it. The separate Firebase SA audit can authenticate a user-supplied owned credential once to enumerate bounded metadata and test permissions without exercising them.

Manual only

FCM

Review sender IDs, token handling, and server-key hygiene without sending messages or validating credentials. Delivery and authorization tests require a controlled manual procedure.

Checklist reference: Icex0/firebase-pentest-checklist. Use it only within your documented authorization and the safety boundaries above.

Recommended production flow

Run the static packet first. Triage findings. Enable network checks only for the specific owned environment that needs validation. Rotate every confirmed embedded credential, then rebuild and rescan.

Input coverageAPK · XAPK · APKM · APKS · AAB · ZIP · JAR · DEX · SO
OutputsUnified JSON report · source tree · stage logs · provider findings
SafetyNo execution · private storage · redaction · bounded extraction · explicit live checks
H

PRIVATE ACCESS

Sign in to HarborData

Use the administrator key to manage every workspace, or a scoped workspace key for one team. The key is held in memory only and is cleared on reload or lock.

ANALYSIS DETAIL

Job