{
	"id": "6a729751-3988-4ac1-9288-afdfbdb08fc2",
	"created_at": "2026-04-06T00:08:12.576596Z",
	"updated_at": "2026-04-10T03:35:21.390444Z",
	"deleted_at": null,
	"sha1_hash": "ad674d99679205ff3d3e14ad58cb1fc258af5d75",
	"title": "GitHub - fatedier/frp: A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 636992,
	"plain_text": "GitHub - fatedier/frp: A fast reverse proxy to help you expose a\r\nlocal server behind a NAT or firewall to the internet.\r\nBy fatedier\r\nArchived: 2026-04-05 19:51:54 UTC\r\ncircleci passing\r\n rreelleeaassee vv00..6688..00 ggoo rreeppoorrtt A + ddoowwnnllooaaddss 12M\r\nREADME | 中文文档\r\nSponsors\r\nfrp is an open source project with its ongoing development made possible entirely by the support of our awesome\r\nsponsors. If you'd like to join them, please consider sponsoring frp's development.\r\nGold Sponsors\r\nThe sovereign cloud that puts you in control\r\nAn open source, self-hosted alternative to public clouds, built for data ownership and privacy\r\nRecall.ai - API for meeting recordings\r\nIf you're looking for a meeting recording API, consider checking out Recall.ai,\r\nan API that records Zoom, Google Meet, Microsoft Teams, in-person meetings, and more.\r\nRequestly - Free \u0026 Open-Source alternative to Postman\r\nAll-in-one platform to Test, Mock and Intercept APIs.\r\nhttps://github.com/fatedier/frp\r\nPage 1 of 31\n\nThe complete IDE crafted for professional Go developers\r\nWhat is frp?\r\nfrp is a fast reverse proxy that allows you to expose a local server located behind a NAT or firewall to the Internet.\r\nIt currently supports TCP and UDP, as well as HTTP and HTTPS protocols, enabling requests to be forwarded\r\nto internal services via domain name.\r\nfrp also offers a P2P connect mode.\r\nTable of Contents\r\nDevelopment Status\r\nAbout V2\r\nArchitecture\r\nExample Usage\r\nAccess your computer in a LAN network via SSH\r\nMultiple SSH services sharing the same port\r\nAccessing Internal Web Services with Custom Domains in LAN\r\nForward DNS query requests\r\nForward Unix Domain Socket\r\nExpose a simple HTTP file server\r\nEnable HTTPS for a local HTTP(S) service\r\nExpose your service privately\r\nP2P Mode\r\nFeatures\r\nConfiguration Files\r\nUsing Environment Variables\r\nSplit Configures Into Different Files\r\nServer Dashboard\r\nClient Admin UI\r\nDynamic Proxy Management (Store)\r\nMonitor\r\nPrometheus\r\nAuthenticating the Client\r\nToken Authentication\r\nOIDC Authentication\r\nhttps://github.com/fatedier/frp\r\nPage 2 of 31\n\nEncryption and Compression\r\nTLS\r\nHot-Reloading frpc configuration\r\nGet proxy status from client\r\nOnly allowing certain ports on the server\r\nPort Reuse\r\nBandwidth Limit\r\nFor Each Proxy\r\nTCP Stream Multiplexing\r\nSupport KCP Protocol\r\nSupport QUIC Protocol\r\nConnection Pooling\r\nLoad balancing\r\nService Health Check\r\nRewriting the HTTP Host Header\r\nSetting other HTTP Headers\r\nGet Real IP\r\nHTTP X-Forwarded-For\r\nProxy Protocol\r\nRequire HTTP Basic Auth (Password) for Web Services\r\nCustom Subdomain Names\r\nURL Routing\r\nTCP Port Multiplexing\r\nConnecting to frps via PROXY\r\nPort range mapping\r\nClient Plugins\r\nServer Manage Plugins\r\nSSH Tunnel Gateway\r\nVirtual Network (VirtualNet)\r\nFeature Gates\r\nAvailable Feature Gates\r\nEnabling Feature Gates\r\nFeature Lifecycle\r\nRelated Projects\r\nContributing\r\nDonation\r\nGitHub Sponsors\r\nPayPal\r\nDevelopment Status\r\nfrp is currently under development. You can try the latest release version in the master branch, or use the dev\r\nbranch to access the version currently in development.\r\nhttps://github.com/fatedier/frp\r\nPage 3 of 31\n\nWe are currently working on version 2 and attempting to perform some code refactoring and improvements.\r\nHowever, please note that it will not be compatible with version 1.\r\nWe will transition from version 0 to version 1 at the appropriate time and will only accept bug fixes and\r\nimprovements, rather than big feature requests.\r\nAbout V2\r\nThe complexity and difficulty of the v2 version are much higher than anticipated. I can only work on its\r\ndevelopment during fragmented time periods, and the constant interruptions disrupt productivity significantly.\r\nGiven this situation, we will continue to optimize and iterate on the current version until we have more free time\r\nto proceed with the major version overhaul.\r\nThe concept behind v2 is based on my years of experience and reflection in the cloud-native domain, particularly\r\nin K8s and ServiceMesh. Its core is a modernized four-layer and seven-layer proxy, similar to envoy. This proxy\r\nitself is highly scalable, not only capable of implementing the functionality of intranet penetration but also\r\napplicable to various other domains. Building upon this highly scalable core, we aim to implement all the\r\ncapabilities of frp v1 while also addressing the functionalities that were previously unachievable or difficult to\r\nimplement in an elegant manner. Furthermore, we will maintain efficient development and iteration capabilities.\r\nIn addition, I envision frp itself becoming a highly extensible system and platform, similar to how we can provide\r\na range of extension capabilities based on K8s. In K8s, we can customize development according to enterprise\r\nneeds, utilizing features such as CRD, controller mode, webhook, CSI, and CNI. In frp v1, we introduced the\r\nconcept of server plugins, which implemented some basic extensibility. However, it relies on a simple HTTP\r\nprotocol and requires users to start independent processes and manage them on their own. This approach is far\r\nfrom flexible and convenient, and real-world demands vary greatly. It is unrealistic to expect a non-profit open-source project maintained by a few individuals to meet everyone's needs.\r\nFinally, we acknowledge that the current design of modules such as configuration management, permission\r\nverification, certificate management, and API management is not modern enough. While we may carry out some\r\noptimizations in the v1 version, ensuring compatibility remains a challenging issue that requires a considerable\r\namount of effort to address.\r\nWe sincerely appreciate your support for frp.\r\nArchitecture\r\nhttps://github.com/fatedier/frp\r\nPage 4 of 31\n\nExample Usage\r\nTo begin, download the latest program for your operating system and architecture from the Release page.\r\nNext, place the frps binary and server configuration file on Server A, which has a public IP address.\r\nFinally, place the frpc binary and client configuration file on Server B, which is located on a LAN that cannot\r\nbe directly accessed from the public internet.\r\nSome antiviruses improperly mark frpc as malware and delete it. This is due to frp being a networking tool\r\ncapable of creating reverse proxies. Antiviruses sometimes flag reverse proxies due to their ability to bypass\r\nfirewall port restrictions. If you are using antivirus, then you may need to whitelist/exclude frpc in your antivirus\r\nsettings to avoid accidental quarantine/deletion. See issue 3637 for more details.\r\nAccess your computer in a LAN network via SSH\r\n1. Modify frps.toml on server A by setting the bindPort for frp clients to connect to:\r\n# frps.toml\r\nbindPort = 7000\r\n2. Start frps on server A:\r\n./frps -c ./frps.toml\r\n3. Modify frpc.toml on server B and set the serverAddr field to the public IP address of your frps server:\r\nhttps://github.com/fatedier/frp\r\nPage 5 of 31\n\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"ssh\"\r\ntype = \"tcp\"\r\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\nremotePort = 6000\r\nNote that the localPort (listened on the client) and remotePort (exposed on the server) are used for traffic\r\ngoing in and out of the frp system, while the serverPort is used for communication between frps and frpc.\r\n4. Start frpc on server B:\r\n./frpc -c ./frpc.toml\r\n5. To access server B from another machine through server A via SSH (assuming the username is test ), use\r\nthe following command:\r\nssh -oPort=6000 test@x.x.x.x\r\nMultiple SSH services sharing the same port\r\nThis example implements multiple SSH services exposed through the same port using a proxy of type tcpmux.\r\nSimilarly, as long as the client supports the HTTP Connect proxy connection method, port reuse can be achieved\r\nin this way.\r\n1. Deploy frps on a machine with a public IP and modify the frps.toml file. Here is a simplified configuration:\r\nbindPort = 7000\r\ntcpmuxHTTPConnectPort = 5002\r\n2. Deploy frpc on the internal machine A with the following configuration:\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"ssh1\"\r\ntype = \"tcpmux\"\r\nmultiplexer = \"httpconnect\"\r\ncustomDomains = [\"machine-a.example.com\"]\r\nhttps://github.com/fatedier/frp\r\nPage 6 of 31\n\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\n3. Deploy another frpc on the internal machine B with the following configuration:\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"ssh2\"\r\ntype = \"tcpmux\"\r\nmultiplexer = \"httpconnect\"\r\ncustomDomains = [\"machine-b.example.com\"]\r\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\n4. To access internal machine A using SSH ProxyCommand, assuming the username is \"test\":\r\nssh -o 'proxycommand socat - PROXY:x.x.x.x:%h:%p,proxyport=5002' test@machine-a.example.com\r\n5. To access internal machine B, the only difference is the domain name, assuming the username is \"test\":\r\nssh -o 'proxycommand socat - PROXY:x.x.x.x:%h:%p,proxyport=5002' test@machine-b.example.com\r\nAccessing Internal Web Services with Custom Domains in LAN\r\nSometimes we need to expose a local web service behind a NAT network to others for testing purposes with our\r\nown domain name.\r\nUnfortunately, we cannot resolve a domain name to a local IP. However, we can use frp to expose an HTTP(S)\r\nservice.\r\n1. Modify frps.toml and set the HTTP port for vhost to 8080:\r\n# frps.toml\r\nbindPort = 7000\r\nvhostHTTPPort = 8080\r\nIf you want to configure an https proxy, you need to set up the vhostHTTPSPort .\r\n2. Start frps :\r\n./frps -c ./frps.toml\r\n3. Modify frpc.toml and set serverAddr to the IP address of the remote frps server. Specify the\r\nlocalPort of your web service:\r\nhttps://github.com/fatedier/frp\r\nPage 7 of 31\n\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"http\"\r\nlocalPort = 80\r\ncustomDomains = [\"www.example.com\"]\r\n4. Start frpc :\r\n./frpc -c ./frpc.toml\r\n5. Map the A record of www.example.com to either the public IP of the remote frps server or a CNAME\r\nrecord pointing to your original domain.\r\n6. Visit your local web service using url http://www.example.com:8080 .\r\nForward DNS query requests\r\n1. Modify frps.toml :\r\n# frps.toml\r\nbindPort = 7000\r\n2. Start frps :\r\n./frps -c ./frps.toml\r\n3. Modify frpc.toml and set serverAddr to the IP address of the remote frps server. Forward DNS query\r\nrequests to the Google Public DNS server 8.8.8.8:53 :\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"dns\"\r\ntype = \"udp\"\r\nlocalIP = \"8.8.8.8\"\r\nlocalPort = 53\r\nremotePort = 6000\r\n4. Start frpc:\r\nhttps://github.com/fatedier/frp\r\nPage 8 of 31\n\n./frpc -c ./frpc.toml\r\n5. Test DNS resolution using the dig command:\r\ndig @x.x.x.x -p 6000 www.google.com\r\nForward Unix Domain Socket\r\nExpose a Unix domain socket (e.g. the Docker daemon socket) as TCP.\r\nConfigure frps as above.\r\n1. Start frpc with the following configuration:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"unix_domain_socket\"\r\ntype = \"tcp\"\r\nremotePort = 6000\r\n[proxies.plugin]\r\ntype = \"unix_domain_socket\"\r\nunixPath = \"/var/run/docker.sock\"\r\n2. Test the configuration by getting the docker version using curl :\r\ncurl http://x.x.x.x:6000/version\r\nExpose a simple HTTP file server\r\nExpose a simple HTTP file server to access files stored in the LAN from the public Internet.\r\nConfigure frps as described above, then:\r\n1. Start frpc with the following configuration:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"test_static_file\"\r\ntype = \"tcp\"\r\nremotePort = 6000\r\n[proxies.plugin]\r\ntype = \"static_file\"\r\nhttps://github.com/fatedier/frp\r\nPage 9 of 31\n\nlocalPath = \"/tmp/files\"\r\nstripPrefix = \"static\"\r\nhttpUser = \"abc\"\r\nhttpPassword = \"abc\"\r\n2. Visit http://x.x.x.x:6000/static/ from your browser and specify correct username and password to\r\nview files in /tmp/files on the frpc machine.\r\nEnable HTTPS for a local HTTP(S) service\r\nYou may substitute https2https for the plugin, and point the localAddr to a HTTPS endpoint.\r\n1. Start frpc with the following configuration:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"test_https2http\"\r\ntype = \"https\"\r\ncustomDomains = [\"test.example.com\"]\r\n[proxies.plugin]\r\ntype = \"https2http\"\r\nlocalAddr = \"127.0.0.1:80\"\r\ncrtPath = \"./server.crt\"\r\nkeyPath = \"./server.key\"\r\nhostHeaderRewrite = \"127.0.0.1\"\r\nrequestHeaders.set.x-from-where = \"frp\"\r\n2. Visit https://test.example.com .\r\nExpose your service privately\r\nTo mitigate risks associated with exposing certain services directly to the public network, STCP (Secret TCP)\r\nmode requires a preshared key to be used for access to the service from other clients.\r\nConfigure frps same as above.\r\n1. Start frpc on machine B with the following config. This example is for exposing the SSH service (port\r\n22), and note the secretKey field for the preshared key, and that the remotePort field is removed here:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\nhttps://github.com/fatedier/frp\r\nPage 10 of 31\n\n[[proxies]]\r\nname = \"secret_ssh\"\r\ntype = \"stcp\"\r\nsecretKey = \"abcdefg\"\r\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\n2. Start another frpc (typically on another machine C) with the following config to access the SSH service\r\nwith a security key ( secretKey field):\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[visitors]]\r\nname = \"secret_ssh_visitor\"\r\ntype = \"stcp\"\r\nserverName = \"secret_ssh\"\r\nsecretKey = \"abcdefg\"\r\nbindAddr = \"127.0.0.1\"\r\nbindPort = 6000\r\n3. On machine C, connect to SSH on machine B, using this command:\r\nssh -oPort=6000 127.0.0.1\r\nP2P Mode\r\nxtcp is designed to transmit large amounts of data directly between clients. A frps server is still needed, as P2P\r\nhere only refers to the actual data transmission.\r\nNote that it may not work with all types of NAT devices. You might want to fallback to stcp if xtcp doesn't work.\r\n1. Start frpc on machine B, and expose the SSH port. Note that the remotePort field is removed:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n# set up a new stun server if the default one is not available.\r\n# natHoleStunServer = \"xxx\"\r\n[[proxies]]\r\nname = \"p2p_ssh\"\r\ntype = \"xtcp\"\r\nsecretKey = \"abcdefg\"\r\nhttps://github.com/fatedier/frp\r\nPage 11 of 31\n\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\n2. Start another frpc (typically on another machine C) with the configuration to connect to SSH using P2P\r\nmode:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n# set up a new stun server if the default one is not available.\r\n# natHoleStunServer = \"xxx\"\r\n[[visitors]]\r\nname = \"p2p_ssh_visitor\"\r\ntype = \"xtcp\"\r\nserverName = \"p2p_ssh\"\r\nsecretKey = \"abcdefg\"\r\nbindAddr = \"127.0.0.1\"\r\nbindPort = 6000\r\n# when automatic tunnel persistence is required, set it to true\r\nkeepTunnelOpen = false\r\n3. On machine C, connect to SSH on machine B, using this command:\r\nssh -oPort=6000 127.0.0.1\r\nFeatures\r\nConfiguration Files\r\nSince v0.52.0, we support TOML, YAML, and JSON for configuration. Please note that INI is deprecated and will\r\nbe removed in future releases. New features will only be available in TOML, YAML, or JSON. Users wanting\r\nthese new features should switch their configuration format accordingly.\r\nRead the full example configuration files to find out even more features not described here.\r\nExamples use TOML format, but you can still use YAML or JSON.\r\nThese configuration files is for reference only. Please do not use this configuration directly to run the program as it\r\nmay have various issues.\r\nFull configuration file for frps (Server)\r\nFull configuration file for frpc (Client)\r\nUsing Environment Variables\r\nhttps://github.com/fatedier/frp\r\nPage 12 of 31\n\nEnvironment variables can be referenced in the configuration file, using Go's standard format:\r\n# frpc.toml\r\nserverAddr = \"{{ .Envs.FRP_SERVER_ADDR }}\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"ssh\"\r\ntype = \"tcp\"\r\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\nremotePort = {{ .Envs.FRP_SSH_REMOTE_PORT }}\r\nWith the config above, variables can be passed into frpc program like this:\r\nexport FRP_SERVER_ADDR=x.x.x.x\r\nexport FRP_SSH_REMOTE_PORT=6000\r\n./frpc -c ./frpc.toml\r\nfrpc will render configuration file template using OS environment variables. Remember to prefix your reference\r\nwith .Envs .\r\nSplit Configures Into Different Files\r\nYou can split multiple proxy configs into different files and include them in the main file.\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\nincludes = [\"./confd/*.toml\"]\r\n# ./confd/test.toml\r\n[[proxies]]\r\nname = \"ssh\"\r\ntype = \"tcp\"\r\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 22\r\nremotePort = 6000\r\nServer Dashboard\r\nCheck frp's status and proxies' statistics information by Dashboard.\r\nhttps://github.com/fatedier/frp\r\nPage 13 of 31\n\nConfigure a port for dashboard to enable this feature:\r\n# The default value is 127.0.0.1. Change it to 0.0.0.0 when you want to access it from a public netwo\r\nwebServer.addr = \"0.0.0.0\"\r\nwebServer.port = 7500\r\n# dashboard's username and password are both optional\r\nwebServer.user = \"admin\"\r\nwebServer.password = \"admin\"\r\nThen visit http://[serverAddr]:7500 to see the dashboard, with username and password both being admin .\r\nAdditionally, you can use HTTPS port by using your domains wildcard or normal SSL certificate:\r\nwebServer.port = 7500\r\n# dashboard's username and password are both optional\r\nwebServer.user = \"admin\"\r\nwebServer.password = \"admin\"\r\nwebServer.tls.certFile = \"server.crt\"\r\nwebServer.tls.keyFile = \"server.key\"\r\nThen visit https://[serverAddr]:7500 to see the dashboard in secure HTTPS connection, with username and\r\npassword both being admin .\r\nClient Admin UI\r\nThe Client Admin UI helps you check and manage frpc's configuration and proxies.\r\nConfigure an address for admin UI to enable this feature:\r\nhttps://github.com/fatedier/frp\r\nPage 14 of 31\n\nwebServer.addr = \"127.0.0.1\"\r\nwebServer.port = 7400\r\nwebServer.user = \"admin\"\r\nwebServer.password = \"admin\"\r\nThen visit http://127.0.0.1:7400 to see admin UI, with username and password both being admin .\r\nDynamic Proxy Management (Store)\r\nYou can dynamically create, update, and delete proxies and visitors at runtime through the Web UI or API, without\r\nrestarting frpc.\r\nTo enable this feature, configure store.path to specify a file for persisting the configurations:\r\n[store]\r\npath = \"./db.json\"\r\nProxies and visitors managed through the Store are saved to disk and automatically restored on frpc restart. They\r\nwork alongside proxies defined in the configuration file — Store entries take precedence when names conflict.\r\nMonitor\r\nWhen web server is enabled, frps will save monitor data in cache for 7 days. It will be cleared after process restart.\r\nPrometheus is also supported.\r\nPrometheus\r\nEnable dashboard first, then configure enablePrometheus = true in frps.toml .\r\nhttp://{dashboard_addr}/metrics will provide prometheus monitor data.\r\nAuthenticating the Client\r\nThere are 2 authentication methods to authenticate frpc with frps.\r\nYou can decide which one to use by configuring auth.method in frpc.toml and frps.toml , the default one is\r\ntoken.\r\nConfiguring auth.additionalScopes = [\"HeartBeats\"] will use the configured authentication method to add\r\nand validate authentication on every heartbeat between frpc and frps.\r\nConfiguring auth.additionalScopes = [\"NewWorkConns\"] will do the same for every new work connection\r\nbetween frpc and frps.\r\nToken Authentication\r\nhttps://github.com/fatedier/frp\r\nPage 15 of 31\n\nWhen specifying auth.method = \"token\" in frpc.toml and frps.toml - token based authentication will be\r\nused.\r\nMake sure to specify the same auth.token in frps.toml and frpc.toml for frpc to pass frps validation\r\nToken Source\r\nfrp supports reading authentication tokens from external sources using the tokenSource configuration. Currently,\r\nfile-based token source is supported.\r\nFile-based token source:\r\n# frpc.toml\r\nauth.method = \"token\"\r\nauth.tokenSource.type = \"file\"\r\nauth.tokenSource.file.path = \"/path/to/token/file\"\r\nThe token will be read from the specified file at startup. This is useful for scenarios where tokens are managed by\r\nexternal systems or need to be kept separate from configuration files for security reasons.\r\nOIDC Authentication\r\nWhen specifying auth.method = \"oidc\" in frpc.toml and frps.toml - OIDC based authentication will be\r\nused.\r\nOIDC stands for OpenID Connect, and the flow used is called Client Credentials Grant.\r\nTo use this authentication type - configure frpc.toml and frps.toml as follows:\r\n# frps.toml\r\nauth.method = \"oidc\"\r\nauth.oidc.issuer = \"https://example-oidc-issuer.com/\"\r\nauth.oidc.audience = \"https://oidc-audience.com/.default\"\r\n# frpc.toml\r\nauth.method = \"oidc\"\r\nauth.oidc.clientID = \"98692467-37de-409a-9fac-bb2585826f18\" # Replace with OIDC client ID\r\nauth.oidc.clientSecret = \"oidc_secret\"\r\nauth.oidc.audience = \"https://oidc-audience.com/.default\"\r\nauth.oidc.tokenEndpointURL = \"https://example-oidc-endpoint.com/oauth2/v2.0/token\"\r\nEncryption and Compression\r\nThe features are off by default. You can turn on encryption and/or compression:\r\nhttps://github.com/fatedier/frp\r\nPage 16 of 31\n\n# frpc.toml\r\n[[proxies]]\r\nname = \"ssh\"\r\ntype = \"tcp\"\r\nlocalPort = 22\r\nremotePort = 6000\r\ntransport.useEncryption = true\r\ntransport.useCompression = true\r\nTLS\r\nSince v0.50.0, the default value of transport.tls.enable and transport.tls.disableCustomTLSFirstByte has\r\nbeen changed to true, and tls is enabled by default.\r\nFor port multiplexing, frp sends a first byte 0x17 to dial a TLS connection. This only takes effect when you set\r\ntransport.tls.disableCustomTLSFirstByte to false.\r\nTo enforce frps to only accept TLS connections - configure transport.tls.force = true in frps.toml .\r\nThis is optional.\r\nfrpc TLS settings:\r\ntransport.tls.enable = true\r\ntransport.tls.certFile = \"certificate.crt\"\r\ntransport.tls.keyFile = \"certificate.key\"\r\ntransport.tls.trustedCaFile = \"ca.crt\"\r\nfrps TLS settings:\r\ntransport.tls.force = true\r\ntransport.tls.certFile = \"certificate.crt\"\r\ntransport.tls.keyFile = \"certificate.key\"\r\ntransport.tls.trustedCaFile = \"ca.crt\"\r\nYou will need a root CA cert and at least one SSL/TLS certificate. It can be self-signed or regular (such as Let's\r\nEncrypt or another SSL/TLS certificate provider).\r\nIf you using frp via IP address and not hostname, make sure to set the appropriate IP address in the Subject\r\nAlternative Name (SAN) area when generating SSL/TLS Certificates.\r\nGiven an example:\r\nPrepare openssl config file. It exists at /etc/pki/tls/openssl.cnf in Linux System and\r\n/System/Library/OpenSSL/openssl.cnf in MacOS, and you can copy it to current path, like cp\r\nhttps://github.com/fatedier/frp\r\nPage 17 of 31\n\n/etc/pki/tls/openssl.cnf ./my-openssl.cnf . If not, you can build it by yourself, like:\r\ncat \u003e my-openssl.cnf \u003c\u003c EOF\r\n[ ca ]\r\ndefault_ca = CA_default\r\n[ CA_default ]\r\nx509_extensions = usr_cert\r\n[ req ]\r\ndefault_bits = 2048\r\ndefault_md = sha256\r\ndefault_keyfile = privkey.pem\r\ndistinguished_name = req_distinguished_name\r\nattributes = req_attributes\r\nx509_extensions = v3_ca\r\nstring_mask = utf8only\r\n[ req_distinguished_name ]\r\n[ req_attributes ]\r\n[ usr_cert ]\r\nbasicConstraints = CA:FALSE\r\nnsComment = \"OpenSSL Generated Certificate\"\r\nsubjectKeyIdentifier = hash\r\nauthorityKeyIdentifier = keyid,issuer\r\n[ v3_ca ]\r\nsubjectKeyIdentifier = hash\r\nauthorityKeyIdentifier = keyid:always,issuer\r\nbasicConstraints = CA:true\r\nEOF\r\nbuild ca certificates:\r\nopenssl genrsa -out ca.key 2048\r\nopenssl req -x509 -new -nodes -key ca.key -subj \"/CN=example.ca.com\" -days 5000 -out ca.crt\r\nbuild frps certificates:\r\nopenssl genrsa -out server.key 2048\r\nopenssl req -new -sha256 -key server.key \\\r\n -subj \"/C=XX/ST=DEFAULT/L=DEFAULT/O=DEFAULT/CN=server.com\" \\\r\n -reqexts SAN \\\r\n -config \u003c(cat my-openssl.cnf \u003c(printf \"\\n[SAN]\\nsubjectAltName=DNS:localhost,IP:127.0.0.1,DNS:example.server\r\n -out server.csr\r\nopenssl x509 -req -days 365 -sha256 \\\r\n-in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial \\\r\nhttps://github.com/fatedier/frp\r\nPage 18 of 31\n\n-extfile \u003c(printf \"subjectAltName=DNS:localhost,IP:127.0.0.1,DNS:example.server.com\") \\\r\n-out server.crt\r\nbuild frpc certificates：\r\nopenssl genrsa -out client.key 2048\r\nopenssl req -new -sha256 -key client.key \\\r\n -subj \"/C=XX/ST=DEFAULT/L=DEFAULT/O=DEFAULT/CN=client.com\" \\\r\n -reqexts SAN \\\r\n -config \u003c(cat my-openssl.cnf \u003c(printf \"\\n[SAN]\\nsubjectAltName=DNS:client.com,DNS:example.client.com\")) \\\r\n -out client.csr\r\nopenssl x509 -req -days 365 -sha256 \\\r\n -in client.csr -CA ca.crt -CAkey ca.key -CAcreateserial \\\r\n-extfile \u003c(printf \"subjectAltName=DNS:client.com,DNS:example.client.com\") \\\r\n-out client.crt\r\nHot-Reloading frpc configuration\r\nThe webServer fields are required for enabling HTTP API:\r\n# frpc.toml\r\nwebServer.addr = \"127.0.0.1\"\r\nwebServer.port = 7400\r\nThen run command frpc reload -c ./frpc.toml and wait for about 10 seconds to let frpc create or update or\r\nremove proxies.\r\nNote that global client parameters won't be modified except 'start'.\r\nstart is a global allowlist evaluated after all sources are merged (config file/include/store). If start is non-empty, any proxy or visitor not listed there will not be started, including entries created via Store API.\r\nstart is kept mainly for compatibility and is generally not recommended for new configurations. Prefer per-proxy/per-visitor enabled , and keep start empty unless you explicitly want this global allowlist behavior.\r\nYou can run command frpc verify -c ./frpc.toml before reloading to check if there are config errors.\r\nGet proxy status from client\r\nUse frpc status -c ./frpc.toml to get status of all proxies. The webServer fields are required for enabling\r\nHTTP API.\r\nOnly allowing certain ports on the server\r\nallowPorts in frps.toml is used to avoid abuse of ports:\r\nhttps://github.com/fatedier/frp\r\nPage 19 of 31\n\n# frps.toml\r\nallowPorts = [\r\n { start = 2000, end = 3000 },\r\n { single = 3001 },\r\n { single = 3003 },\r\n { start = 4000, end = 50000 }\r\n]\r\nPort Reuse\r\nvhostHTTPPort and vhostHTTPSPort in frps can use same port with bindPort . frps will detect the\r\nconnection's protocol and handle it correspondingly.\r\nWhat you need to pay attention to is that if you want to configure vhostHTTPSPort and bindPort to the same\r\nport, you need to first set transport.tls.disableCustomTLSFirstByte to false.\r\nWe would like to try to allow multiple proxies bind a same remote port with different protocols in the future.\r\nBandwidth Limit\r\nFor Each Proxy\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"ssh\"\r\ntype = \"tcp\"\r\nlocalPort = 22\r\nremotePort = 6000\r\ntransport.bandwidthLimit = \"1MB\"\r\nSet transport.bandwidthLimit in each proxy's configure to enable this feature. Supported units are MB and\r\nKB .\r\nSet transport.bandwidthLimitMode to client or server to limit bandwidth on the client or server side.\r\nDefault is client .\r\nTCP Stream Multiplexing\r\nfrp supports tcp stream multiplexing since v0.10.0 like HTTP2 Multiplexing, in which case all logic connections\r\nto the same frpc are multiplexed into the same TCP connection.\r\nYou can disable this feature by modify frps.toml and frpc.toml :\r\nhttps://github.com/fatedier/frp\r\nPage 20 of 31\n\n# frps.toml and frpc.toml, must be same\r\ntransport.tcpMux = false\r\nSupport KCP Protocol\r\nKCP is a fast and reliable protocol that can achieve the transmission effect of a reduction of the average latency by\r\n30% to 40% and reduction of the maximum delay by a factor of three, at the cost of 10% to 20% more bandwidth\r\nwasted than TCP.\r\nKCP mode uses UDP as the underlying transport. Using KCP in frp:\r\n1. Enable KCP in frps:\r\n# frps.toml\r\nbindPort = 7000\r\n# Specify a UDP port for KCP.\r\nkcpBindPort = 7000\r\nThe kcpBindPort number can be the same number as bindPort , since bindPort field specifies a TCP port.\r\n2. Configure frpc.toml to use KCP to connect to frps:\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\n# Same as the 'kcpBindPort' in frps.toml\r\nserverPort = 7000\r\ntransport.protocol = \"kcp\"\r\nSupport QUIC Protocol\r\nQUIC is a new multiplexed transport built on top of UDP.\r\nUsing QUIC in frp:\r\n1. Enable QUIC in frps:\r\n# frps.toml\r\nbindPort = 7000\r\n# Specify a UDP port for QUIC.\r\nquicBindPort = 7000\r\nThe quicBindPort number can be the same number as bindPort , since bindPort field specifies a TCP port.\r\n2. Configure frpc.toml to use QUIC to connect to frps:\r\nhttps://github.com/fatedier/frp\r\nPage 21 of 31\n\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\n# Same as the 'quicBindPort' in frps.toml\r\nserverPort = 7000\r\ntransport.protocol = \"quic\"\r\nConnection Pooling\r\nBy default, frps creates a new frpc connection to the backend service upon a user request. With connection\r\npooling, frps keeps a certain number of pre-established connections, reducing the time needed to establish a\r\nconnection.\r\nThis feature is suitable for a large number of short connections.\r\n1. Configure the limit of pool count each proxy can use in frps.toml :\r\n# frps.toml\r\ntransport.maxPoolCount = 5\r\n2. Enable and specify the number of connection pool:\r\n# frpc.toml\r\ntransport.poolCount = 1\r\nLoad balancing\r\nLoad balancing is supported by group .\r\nThis feature is only available for types tcp , http , tcpmux now.\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"test1\"\r\ntype = \"tcp\"\r\nlocalPort = 8080\r\nremotePort = 80\r\nloadBalancer.group = \"web\"\r\nloadBalancer.groupKey = \"123\"\r\n[[proxies]]\r\nname = \"test2\"\r\ntype = \"tcp\"\r\nlocalPort = 8081\r\nremotePort = 80\r\nhttps://github.com/fatedier/frp\r\nPage 22 of 31\n\nloadBalancer.group = \"web\"\r\nloadBalancer.groupKey = \"123\"\r\nloadBalancer.groupKey is used for authentication.\r\nConnections to port 80 will be dispatched to proxies in the same group randomly.\r\nFor type tcp , remotePort in the same group should be the same.\r\nFor type http , customDomains , subdomain , locations should be the same.\r\nService Health Check\r\nHealth check feature can help you achieve high availability with load balancing.\r\nAdd healthCheck.type = \"tcp\" or healthCheck.type = \"http\" to enable health check.\r\nWith health check type tcp, the service port will be pinged (TCPing):\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"test1\"\r\ntype = \"tcp\"\r\nlocalPort = 22\r\nremotePort = 6000\r\n# Enable TCP health check\r\nhealthCheck.type = \"tcp\"\r\n# TCPing timeout seconds\r\nhealthCheck.timeoutSeconds = 3\r\n# If health check failed 3 times in a row, the proxy will be removed from frps\r\nhealthCheck.maxFailed = 3\r\n# A health check every 10 seconds\r\nhealthCheck.intervalSeconds = 10\r\nWith health check type http, an HTTP request will be sent to the service and an HTTP 2xx OK response is\r\nexpected:\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"http\"\r\nlocalIP = \"127.0.0.1\"\r\nlocalPort = 80\r\ncustomDomains = [\"test.example.com\"]\r\n# Enable HTTP health check\r\nhttps://github.com/fatedier/frp\r\nPage 23 of 31\n\nhealthCheck.type = \"http\"\r\n# frpc will send a GET request to '/status'\r\n# and expect an HTTP 2xx OK response\r\nhealthCheck.path = \"/status\"\r\nhealthCheck.timeoutSeconds = 3\r\nhealthCheck.maxFailed = 3\r\nhealthCheck.intervalSeconds = 10\r\nRewriting the HTTP Host Header\r\nBy default frp does not modify the tunneled HTTP requests at all as it's a byte-for-byte copy.\r\nHowever, speaking of web servers and HTTP requests, your web server might rely on the Host HTTP header to\r\ndetermine the website to be accessed. frp can rewrite the Host header when forwarding the HTTP requests, with\r\nthe hostHeaderRewrite field:\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"http\"\r\nlocalPort = 80\r\ncustomDomains = [\"test.example.com\"]\r\nhostHeaderRewrite = \"dev.example.com\"\r\nThe HTTP request will have the Host header rewritten to Host: dev.example.com when it reaches the actual\r\nweb server, although the request from the browser probably has Host: test.example.com .\r\nSetting other HTTP Headers\r\nSimilar to Host , You can override other HTTP request and response headers with proxy type http .\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"http\"\r\nlocalPort = 80\r\ncustomDomains = [\"test.example.com\"]\r\nhostHeaderRewrite = \"dev.example.com\"\r\nrequestHeaders.set.x-from-where = \"frp\"\r\nresponseHeaders.set.foo = \"bar\"\r\nIn this example, it will set header x-from-where: frp in the HTTP request and foo: bar in the HTTP\r\nresponse.\r\nhttps://github.com/fatedier/frp\r\nPage 24 of 31\n\nGet Real IP\r\nHTTP X-Forwarded-For\r\nThis feature is for http proxies or proxies with the https2http and https2https plugins enabled.\r\nYou can get user's real IP from HTTP request headers X-Forwarded-For .\r\nProxy Protocol\r\nfrp supports Proxy Protocol to send user's real IP to local services.\r\nHere is an example for https service:\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"https\"\r\nlocalPort = 443\r\ncustomDomains = [\"test.example.com\"]\r\n# now v1 and v2 are supported\r\ntransport.proxyProtocolVersion = \"v2\"\r\nYou can enable Proxy Protocol support in nginx to expose user's real IP in HTTP header X-Real-IP , and then\r\nread X-Real-IP header in your web service for the real IP.\r\nRequire HTTP Basic Auth (Password) for Web Services\r\nAnyone who can guess your tunnel URL can access your local web server unless you protect it with a password.\r\nThis enforces HTTP Basic Auth on all requests with the username and password specified in frpc's configure file.\r\nIt can only be enabled when proxy type is http.\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"http\"\r\nlocalPort = 80\r\ncustomDomains = [\"test.example.com\"]\r\nhttpUser = \"abc\"\r\nhttpPassword = \"abc\"\r\nhttps://github.com/fatedier/frp\r\nPage 25 of 31\n\nVisit http://test.example.com in the browser and now you are prompted to enter the username and password.\r\nCustom Subdomain Names\r\nIt is convenient to use subdomain configure for http and https types when many people share one frps server.\r\n# frps.toml\r\nsubDomainHost = \"frps.com\"\r\nResolve *.frps.com to the frps server's IP. This is usually called a Wildcard DNS record.\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web\"\r\ntype = \"http\"\r\nlocalPort = 80\r\nsubdomain = \"test\"\r\nNow you can visit your web service on test.frps.com .\r\nNote that if subdomainHost is not empty, customDomains should not be the subdomain of subdomainHost .\r\nURL Routing\r\nfrp supports forwarding HTTP requests to different backend web services by url routing.\r\nlocations specifies the prefix of URL used for routing. frps first searches for the most specific prefix location\r\ngiven by literal strings regardless of the listed order.\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"web01\"\r\ntype = \"http\"\r\nlocalPort = 80\r\ncustomDomains = [\"web.example.com\"]\r\nlocations = [\"/\"]\r\n[[proxies]]\r\nname = \"web02\"\r\ntype = \"http\"\r\nlocalPort = 81\r\ncustomDomains = [\"web.example.com\"]\r\nlocations = [\"/news\", \"/about\"]\r\nhttps://github.com/fatedier/frp\r\nPage 26 of 31\n\nHTTP requests with URL prefix /news or /about will be forwarded to web02 and other requests to web01.\r\nTCP Port Multiplexing\r\nfrp supports receiving TCP sockets directed to different proxies on a single port on frps, similar to\r\nvhostHTTPPort and vhostHTTPSPort .\r\nThe only supported TCP port multiplexing method available at the moment is httpconnect - HTTP CONNECT\r\ntunnel.\r\nWhen setting tcpmuxHTTPConnectPort to anything other than 0 in frps, frps will listen on this port for HTTP\r\nCONNECT requests.\r\nThe host of the HTTP CONNECT request will be used to match the proxy in frps. Proxy hosts can be configured\r\nin frpc by configuring customDomains and / or subdomain under tcpmux proxies, when multiplexer =\r\n\"httpconnect\" .\r\nFor example:\r\n# frps.toml\r\nbindPort = 7000\r\ntcpmuxHTTPConnectPort = 1337\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\n[[proxies]]\r\nname = \"proxy1\"\r\ntype = \"tcpmux\"\r\nmultiplexer = \"httpconnect\"\r\ncustomDomains = [\"test1\"]\r\nlocalPort = 80\r\n[[proxies]]\r\nname = \"proxy2\"\r\ntype = \"tcpmux\"\r\nmultiplexer = \"httpconnect\"\r\ncustomDomains = [\"test2\"]\r\nlocalPort = 8080\r\nIn the above configuration - frps can be contacted on port 1337 with a HTTP CONNECT header such as:\r\nCONNECT test1 HTTP/1.1\\r\\n\\r\\n\r\nhttps://github.com/fatedier/frp\r\nPage 27 of 31\n\nand the connection will be routed to proxy1 .\r\nConnecting to frps via PROXY\r\nfrpc can connect to frps through proxy if you set OS environment variable HTTP_PROXY , or if\r\ntransport.proxyURL is set in frpc.toml file.\r\nIt only works when protocol is tcp.\r\n# frpc.toml\r\nserverAddr = \"x.x.x.x\"\r\nserverPort = 7000\r\ntransport.proxyURL = \"http://user:pwd@192.168.1.128:8080\"\r\nPort range mapping\r\nAdded in v0.56.0\r\nWe can use the range syntax of Go template combined with the built-in parseNumberRangePair function to\r\nachieve port range mapping.\r\nThe following example, when run, will create 8 proxies named test-6000, test-6001 ... test-6007 , each\r\nmapping the remote port to the local port.\r\n{{- range $_, $v := parseNumberRangePair \"6000-6006,6007\" \"6000-6006,6007\" }}\r\n[[proxies]]\r\nname = \"tcp-{{ $v.First }}\"\r\ntype = \"tcp\"\r\nlocalPort = {{ $v.First }}\r\nremotePort = {{ $v.Second }}\r\n{{- end }}\r\nClient Plugins\r\nfrpc only forwards requests to local TCP or UDP ports by default.\r\nPlugins are used for providing rich features. There are built-in plugins such as unix_domain_socket ,\r\nhttp_proxy , socks5 , static_file , http2https , https2http , https2https and you can see example\r\nusage.\r\nUsing plugin http_proxy:\r\n# frpc.toml\r\n[[proxies]]\r\nname = \"http_proxy\"\r\nhttps://github.com/fatedier/frp\r\nPage 28 of 31\n\ntype = \"tcp\"\r\nremotePort = 6000\r\n[proxies.plugin]\r\ntype = \"http_proxy\"\r\nhttpUser = \"abc\"\r\nhttpPassword = \"abc\"\r\nhttpUser and httpPassword are configuration parameters used in http_proxy plugin.\r\nServer Manage Plugins\r\nRead the document.\r\nFind more plugins in gofrp/plugin.\r\nSSH Tunnel Gateway\r\nadded in v0.53.0\r\nfrp supports listening to an SSH port on the frps side and achieves TCP protocol proxying through the SSH -R\r\nprotocol, without relying on frpc.\r\n# frps.toml\r\nsshTunnelGateway.bindPort = 2200\r\nWhen running ./frps -c frps.toml , a private key file named .autogen_ssh_key will be automatically created\r\nin the current working directory. This generated private key file will be used by the SSH server in frps.\r\nExecuting the command\r\nssh -R :80:127.0.0.1:8080 v0@{frp address} -p 2200 tcp --proxy_name \"test-tcp\" --remote_port 9090\r\nsets up a proxy on frps that forwards the local 8080 service to the port 9090.\r\nfrp (via SSH) (Ctrl+C to quit)\r\nUser:\r\nProxyName: test-tcp\r\nType: tcp\r\nRemoteAddress: :9090\r\nThis is equivalent to:\r\nfrpc tcp --proxy_name \"test-tcp\" --local_ip 127.0.0.1 --local_port 8080 --remote_port 9090\r\nhttps://github.com/fatedier/frp\r\nPage 29 of 31\n\nPlease refer to this document for more information.\r\nVirtual Network (VirtualNet)\r\nAlpha feature added in v0.62.0\r\nThe VirtualNet feature enables frp to create and manage virtual network connections between clients and visitors\r\nthrough a TUN interface. This allows for IP-level routing between machines, extending frp beyond simple port\r\nforwarding to support full network connectivity.\r\nFor detailed information about configuration and usage, please refer to the VirtualNet documentation.\r\nFeature Gates\r\nfrp supports feature gates to enable or disable experimental features. This allows users to try out new features\r\nbefore they're considered stable.\r\nAvailable Feature Gates\r\nName Stage Default Description\r\nVirtualNet ALPHA false Virtual network capabilities for frp\r\nEnabling Feature Gates\r\nTo enable an experimental feature, add the feature gate to your configuration:\r\nfeatureGates = { VirtualNet = true }\r\nFeature Lifecycle\r\nFeatures typically go through three stages:\r\n1. ALPHA: Disabled by default, may be unstable\r\n2. BETA: May be enabled by default, more stable but still evolving\r\n3. GA (Generally Available): Enabled by default, ready for production use\r\nRelated Projects\r\ngofrp/plugin - A repository for frp plugins that contains a variety of plugins implemented based on the frp\r\nextension mechanism, meeting the customization needs of different scenarios.\r\ngofrp/tiny-frpc - A lightweight version of the frp client (around 3.5MB at minimum) implemented using the\r\nssh protocol, supporting some of the most commonly used features, suitable for devices with limited\r\nresources.\r\nhttps://github.com/fatedier/frp\r\nPage 30 of 31\n\nContributing\r\nInterested in getting involved? We would like to help you!\r\nTake a look at our issues list and consider sending a Pull Request to dev branch.\r\nIf you want to add a new feature, please create an issue first to describe the new feature, as well as the\r\nimplementation approach. Once a proposal is accepted, create an implementation of the new features and\r\nsubmit it as a pull request.\r\nSorry for my poor English. Improvements for this document are welcome, even some typo fixes.\r\nIf you have great ideas, send an email to fatedier@gmail.com.\r\nNote: We prefer you to give your advise in issues, so others with a same question can search it quickly and\r\nwe don't need to answer them repeatedly.\r\nDonation\r\nIf frp helps you a lot, you can support us by:\r\nGitHub Sponsors\r\nSupport us by Github Sponsors.\r\nYou can have your company's logo placed on README file of this project.\r\nPayPal\r\nDonate money by PayPal to my account fatedier@gmail.com.\r\nSource: https://github.com/fatedier/frp\r\nhttps://github.com/fatedier/frp\r\nPage 31 of 31",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"ETDA",
		"MITRE"
	],
	"references": [
		"https://github.com/fatedier/frp"
	],
	"report_names": [
		"frp"
	],
	"threat_actors": [
		{
			"id": "2864e40a-f233-4618-ac61-b03760a41cbb",
			"created_at": "2023-12-01T02:02:34.272108Z",
			"updated_at": "2026-04-10T02:00:04.97558Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "ETDA:WildCard",
			"tools": [
				"RustDown",
				"SysJoker"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "256a6a2d-e8a2-4497-b399-628a7fad4b3e",
			"created_at": "2023-11-30T02:00:07.299845Z",
			"updated_at": "2026-04-10T02:00:03.484788Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "MISPGALAXY:WildCard",
			"tools": [],
			"source_id": "MISPGALAXY",
			"reports": null
		}
	],
	"ts_created_at": 1775434092,
	"ts_updated_at": 1775792121,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/ad674d99679205ff3d3e14ad58cb1fc258af5d75.pdf",
		"text": "https://archive.orkl.eu/ad674d99679205ff3d3e14ad58cb1fc258af5d75.txt",
		"img": "https://archive.orkl.eu/ad674d99679205ff3d3e14ad58cb1fc258af5d75.jpg"
	}
}