- transport
- tcp · udp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 3/10
- lookups
- 3,550
2 transports registered
payload readable on path
used by convention
caution
rank 991 of 993 · top 100%
1 other service is registered on port 4664. compare all 2 →
Technical Details
what runs on :4664The Offline Asset Server for Wrapper is designed specifically for managing and serving assets for applications built using Wrapper: Offline. It operates over TCP and UDP protocols, allowing efficient handling of asset retrieval and storage.
This server utilizes Node.js for asynchronous request processing, which helps in minimizing latency during asset distribution. The use of caching mechanisms enhances performance by reducing load times for frequently requested resources. Additionally, it handles error management gracefully to ensure a smooth user experience.
In versions 1.2.0 and above, the asset server becomes essential for functionality, ensuring that all external API requests are handled in a unified manner without compromising on reliability or scalability.
Security Information
exposure of :4664risk score
3/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
web services averages 3.9 across 112 ports — this one sits 0.9 below.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp · udp
udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite
security overview
Common Vulnerabilities: The primary risks associated with using Wrapper: Offline Asset Server include exposure to Denial of Service (DoS) attacks, improper input validation that may lead to injection attacks, and potential data leakage due to unsecured storage.
Common Mitigations: To mitigate these vulnerabilities, use security best practices such as input validation, implementing rate limiting to prevent abuse, and ensuring all data stored on the server is encrypted. Regular updates and patches to the Node.js environment and any libraries in use can also help close any security gaps.
Related Ports
the 8 most looked-up other ports in web services — 112 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8888 | Sun Answerbook & Alt HTTP | TCP | Web Services | caution | 123.9k |
| :8000 | Intel Remote Desktop / Alternate HTTP Port | TCP | Web Services | safe | 84.3k |
| :8888 | NewsEDGE | TCPUDP | Web Services | caution | 83.3k |
| :8888 | HTTP Alternative Port | TCP | Web Services | caution | 76.5k |
| :8888 | GNUmp3d Streaming HTTP | TCP | Web Services | caution | 76.3k |
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :8881 | Atlasz Secure Server | TCP | Web Services | caution | 67.6k |
| :80 | HTTP | TCPUDP | Web Services | caution | 67.3k |
risk mix of the 8 listed
- safe13%
- caution88%
0 of 8 encrypted