🚢 Shipping Container
An ISO container identifier — trackable across ports, vessels, and customs events.
Trade
Sources
0
0 no-auth
Disciplines
0
that use it
Mission domains
0
reach
Workbench
—
native tool
🔗 Analyst pivots
🔍 Lookup
📜 Playbook — Shipping Container exploitation
- Direction — frame the requirement for Shipping Container: what decision does this support, by when?
- Collection — pull the 0 mapped sources (0 free) and the native workbench; capture provenance and observe OPSEC.
- Processing — normalize, de-duplicate and enrich the collected data.
- Analysis — correlate against local holdings; apply ACH; assign confidence.
- Dissemination — open a case, draft a report, share via STIX/MISP.
- Feedback — set an alert rule / watchlist to monitor for change.
⚡ AI Skills & Automation
Automate unattended via the cron pipeline (collect → ingest → resolve → enrich → score → alert).
🧩 Advanced Capabilities
✨ Enrichment pathways
🎫 Shipping Container
A shipping container is a standardized intermodal freight box identified by an ISO 6346 owner-code and serial number, used to move cargo across ocean, rail and road. In investigations it links a physical consignment to carriers, bills of lading, ports of loading/discharge and consignees, exposing trade-based money laundering, sanctions evasion and smuggling routes.
Format: ISO 6346: 4-letter prefix (3 owner code + equipment category U/J/Z) + 6 serial digits + 1 check digit (e.g. MSKU1234565). Check digit validated via ISO 6346 modulo-11 algorithm.
📡 How it is collected
- Bill of lading / manifest data (e.g. import records, ImportGenius/Panjiva feeds)
- Carrier and terminal container-tracking portals
- AIS-linked port call and gate-move records
- Customs seizure and inspection reports
- Physical observation / photographs of container markings
- EDI messages (BAPLIE stowage plans, CODECO gate moves)
📚 Enrichment & validation sources
🔗 Pivot to
🧩 Analysis & hunting techniques
- ISO 6346 check-digit verification to spot fabricated numbers
- Owner-prefix attribution to leasing company or line
- Route reconstruction across transshipment hubs
- Consignee/shipper network clustering from BL co-occurrence
- Dwell-time and reefer-anomaly detection
- Under/over-invoicing detection via commodity vs weight mismatch
- Sanctioned-entity screening of shipper/consignee
🔧 Tools
- ImportYeti
- Panjiva / S&P Global
- MarineTraffic
- BIC BoxTech database
- Datalastic API
- OpenCorporates
- Maltego
⚡ Workbench actions
- Validate ISO 6346 check digit
- Resolve owner prefix to line/lessor
- Pull bill-of-lading history
- Link to carrying vessel and voyage
- Reconstruct port-to-port route
- Screen shipper/consignee against sanctions
- Cluster by consignee network
- Flag commodity/weight anomalies
📊 Dashboard KPIs
Valid vs invalid check digits (%)Distinct shipper/consignee entities linkedSanctioned-party hitsTransshipment hops per routeReefer/weight anomaly count
📂 Open
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Explore related tools below
- Automate recurring work via cron