467
Summary
- // typical exposure
- Anomalous (rarely legitimately open) — No protocol specification or documented legitimate deployment exists for mylex-mapd, and scan telemetry records zero observed opens for 467/tcp, so any traffic on this port should be treated as anomalous and investigated rather than assumed legitimate.
- // analyst note
- An open 467/tcp has no documented legitimate use and a zero-observed-open baseline, so treat it as an anomaly signal — investigate rather than assume routine service traffic.
- // if you see it open
- No CVE specific to port 467 or mylex-mapd found as of an August 2026 search. No directly quotable primary source confirms a malware/trojan association; unverifiable AI-generated search summaries claiming one were excluded. No forum, vendor doc, or blog post reporting real-world traffic on 467/tcp was found. The port is essentially never legitimately open, so any observed traffic should be treated as anomalous and investigated.
About port 467/tcp.
Port 467/tcp carries the IANA-registered service name mylex-mapd; no protocol specification, RFC, or vendor documentation exists for it, so it should be treated as anomalous rather than as legitimate infrastructure — it is essentially never observed open and should stay off any public-facing host.
IANA's Service Name and Transport Protocol Port Number Registry assigns mylex-mapd to both 467/tcp and 467/udp, credited to assignee Gary Lewis. The Reference column is blank — no RFC or other standards document backs the entry — and the only description text IANA publishes is the name itself, repeated verbatim.
The name plausibly points to a management or access-point daemon tied to Mylex, a RAID and storage-controller hardware vendor active in the 1990s that IBM acquired in 2001, but no primary source ties the registration text to that company or explains what the protocol actually does. That etymology is inference, not a confirmed fact, and is presented here only as a hedge, not a claim.
The port-data corpus derived from nmap-services records an open-frequency of exactly 0 for 467/tcp — a genuine sampled reading of zero observed opens across the scan corpus, not a missing data point — while 467/udp shows a small nonzero frequency of about 0.000445. A Juniper Networks Threat Labs application-signature page restates the IANA registration text for "MYLEX-MAPD" but its own traffic-matching signature keys on an unrelated port set, so even that secondary source stops short of claiming real traffic is seen on 467/tcp.
- IANA assignment
mylex-mapd— description "mylex-mapd" (name repeated verbatim); reference column blank; assignee Gary Lewis; dual-registered 467/tcp + 467/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry mylex-mapd 467/tcp- Range class
- well-known/system (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry mylex-mapd 467/tcp
- Prevalence
- 467/tcp open-frequency = 0 (sampled, zero observed opens); 467/udp open-frequency ≈ 0.000445 [Confirmed] — this site's own tooling
- Related ports
- 467/udp (same
mylex-mapddual registration, blank reference) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry mylex-mapd 467/udp
Primary use
Unknown — no protocol specification, RFC, or vendor documentation is published for mylex-mapd
Other/unofficial uses
possibly a Mylex RAID/storage-controller management daemon (name etymology only, unconfirmed)
Security implications
no CVE and no confirmed malware/trojan association as of an August 2026 search; essentially never legitimately open
Typically seen on
no confirmed hosts; treat any responsive 467/tcp as an anomaly worth investigating [Unknown]
- Analyst note
- An open 467/tcp has no documented legitimate use and a zero-observed-open baseline, so treat it as an anomaly signal — investigate rather than assume routine service traffic.
About port 467/udp.
Port 467/udp carries the IANA-registered service name mylex-mapd; no protocol specification, RFC, or vendor documentation exists for it, so it should be treated as anomalous rather than as legitimate infrastructure.
IANA registers 467 identically on both tcp and udp as mylex-mapd, assignee Gary Lewis, with no RFC or reference cited and no free-text description beyond the service name itself.
The name plausibly traces to Mylex Corporation, a maker of SCSI/RAID disk-array controllers acquired by IBM in 2001, with "mapd" reading as a management-access/agent protocol daemon — but IANA states none of that explicitly, so the link is an inference from the name, not a documented fact.
The repo's port-data.json artifact (built from nmap-services) records 467/udp at an open-frequency of approximately 0.000445 (about 0.04% of scanned hosts), while 467/tcp measures exactly 0 — a real sampled reading of "not observed open," not an absence of data.
No CVE is recorded in the NVD as of an August 2026 search for udp/467 or "mylex," and no malware association could be confirmed: a Juniper ThreatLabs application-signature page for MYLEX-MAPD listed a different port set that excluded 467, and portsmaster.net, a prior source of unverified port-467 claims, now 301-redirects to an unrelated site.
- IANA assignment
mylex-mapd— no free-text description beyond the service name; reference (blank — no RFC cited); assignee Gary Lewis; dual-registered 467/tcp + 467/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry mylex-mapd 467/udp- Range class
- well-known (0-1023) [Confirmed]
- Prevalence
- port-data.json (built from nmap-services) records 467/udp open-frequency ≈0.000445 (~0.04%); 467/tcp ≈0.000000 (sampled, not observed open) [Confirmed] — this site's own tooling (built via this site's own tooling)
- Related ports
- 467/tcp (same
mylex-mapddual registration, blank reference) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry mylex-mapd 467/tcp
Primary use
Unknown — no protocol specification, RFC, or vendor documentation is published for mylex-mapd; the name plausibly points to Mylex Corporation (SCSI/RAID controllers, acquired by IBM 2001), but that is an unconfirmed inference from the name, not an IANA-stated fact
Other/unofficial uses
none confirmed; no independently verifiable community sighting of specific software using udp/467 surfaced in an August 2026 web search [Unknown]
Security implications
no CVE recorded in the NVD as of an August 2026 search for udp/467 or "mylex"; no malware/trojan association confirmed, with candidate sources excluded as unusable (Juniper ThreatLabs MYLEX-MAPD signature page's port list omitted 467; portsmaster.net now redirects to an unrelated site; auditmypc.com content did not load for direct verification) [Unknown]
Typically seen on
no confirmed hosts; anomaly if seen [Unknown]
- Analyst note
- an open udp/467 is statistically rare and thinly documented — investigate observed traffic rather than assume routine activity, given how little independent corroboration exists for this service.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| mylex-mapd | UDP | — | 0.04% |
| mylex-mapd | TCP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.