Hunt IO Details Techniques for Detecting Exposed PrismX Deployments

Summary
Hunt IO demonstrates how to identify PrismX login pages using certificate, HTTP-header, and HTML fingerprints, and reports finding servers also associated with Cobalt Strike.
Key points
- PrismX is a cross-platform penetration-testing toolkit with scanning, exploitation, and shellcode-generation capabilities.
- The article recommends reviewing source code and running untrusted software only in a patched, isolated virtual machine.
- Potential detection clues include the login-page title, self-signed certificate attributes, HTTP response-header hash, and login-page HTML hash.
- The author used Python Requests to inspect PrismX’s login-page responses and developed search criteria based on observed fingerprints.
- Hunt IO identified PrismX-hosting servers that were also associated with Cobalt Strike; the article notes that further research is needed to establish relationships among the infrastructure.
- The article cautions against accessing identified servers without authorization and notes that changing the page title can undermine a detection query.
Article Details
- Defense Focus
- Identify potential PrismX deployments by fingerprinting their login pages and associated network services.
- Detection Methods
- Search for the login-page title "Prism X" alongside the reported HTTP response-header SHA-256 hash.
- Fingerprint the self-signed TLS certificate, including its reported country, state/province, organization, and lack of a common name.
- Use the reported JARM value as a network-service fingerprint.
- Compare HTTP response headers and login-page HTML against the characteristics observed in the lab.
- Review port and certificate history and investigate associated Cobalt Strike infrastructure.
- Data Sources
- HTTP response headers
- Login-page HTML and title
- TLS certificate details
- JARM fingerprint
- Port and certificate history
- Cobalt Strike watermark associations
- Rule Types
- Pseudo query combining a JARM fingerprint with an HTTP response-header SHA-256 hash
- Search for the HTTP response-header hash and a matching webpage title
- Platforms
- Hunt
- Defensive Actions
- Run untrusted software only in a fully patched, isolated virtual machine with a clean snapshot.
- Review source code before downloading or executing software.
- Use the observed fingerprints to hunt for potential deployments, then validate results to reduce false positives.
- Do not access identified servers without proper authorization.
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| SHA256 | cf8e3dfb6292ae09f55df22211db7de7bbbcd5a488bf2b21ec0a1af5598f01e7 | HTTP response-header hash presented as a fingerprint for detecting PrismX login pages. |
Products
Tools
Cobalt Strikethe same JARM hash as earlier in our sample query. Additionally, the server appeared to be hosting a Cobalt Strike team server, suggesting a potential multi-tool deployment.PrismXDescribed on its GitHub README as an "Integrated lightweight cross-platform penetration system," PrismX goes beyond basic vulnerability scanning, offering an exploitation engine, a shellcode generator, and even an SMTP
