Vulnerability Scan Result

Target:

http://malak.com.pk/ (redirect)

Scanned target: https://malak.com.pk/

Submitted: Jun 20, 2026 from FR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Malak \| Trusted Online Cosmetic Store in Pakistan – The Divine Beauty
Description:	Shop authentic cosmetics, skincare, and perfumes at Malak. Trusted online cosmetic store offering premium products, great prices, and fast delivery in Pakistan.

IP Information

ip_address	104.21.57.30
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	172.67.188.233
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	https-alt	cloudflare -

Web Technologies

Software / Version	Category
Bogos	Shopify apps
Facebook Pixel 2.9.349	Analytics
core-js 3.37.0	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
lit-element 4.2.2	JavaScript libraries
MySQL	Databases
Glider.js	JavaScript libraries
Open Graph	Miscellaneous
PageFly	Page builders
PayPal	Payment processors
PHP	Programming languages
Preact	JavaScript libraries
PushOwl	Marketing automation
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Swiper	JavaScript libraries
Priority Hints	Performance
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
jsDelivr	CDN
HSTS	Security
Secomapp	Shopify apps
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://malak.com.pk/	localization, _shopify_y, _shopify_s	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: localization=PK Set-Cookie: _shopify_y=3bae5731-206c-4d1d-abd1-3b29d94b8e84 Set-Cookie: _shopify_s=0a06ce7f-3947-4ede-91ea-b7e9f79f63e6

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://malak.com.pk/	localization, _shopify_y, _shopify_s	Set-Cookie: localization=PK Set-Cookie: _shopify_y=3bae5731-206c-4d1d-abd1-3b29d94b8e84 Set-Cookie: _shopify_s=0a06ce7f-3947-4ede-91ea-b7e9f79f63e6

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://malak.com.pk/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://malak.com.pk/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Evidence

URL Evidence

URL	Evidence
https://malak.com.pk/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.`

https://malak.com.pk/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Bogos	Shopify apps
Facebook Pixel 2.9.349	Analytics
core-js 3.37.0	JavaScript libraries
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
lit-element 4.2.2	JavaScript libraries
MySQL	Databases
Glider.js	JavaScript libraries
Open Graph	Miscellaneous
PageFly	Page builders
PayPal	Payment processors
PHP	Programming languages
Preact	JavaScript libraries
PushOwl	Marketing automation
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Swiper	JavaScript libraries
Priority Hints	Performance
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
jsDelivr	CDN
HSTS	Security
Secomapp	Shopify apps
Cart Functionality	Ecommerce

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://malak.com.pk/	GET	Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	Suspicious comment bug found in: `<!-- BEGIN app snippet: log-debug -->`

Vulnerability description

We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.

Risk description

The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.

Recommendation

Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.

Classification

CWE	CWE-546
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://malak.com.pk/	GET	Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	Email Address: support@malak.com.pk

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://malak.com.pk/.well-known/security.txt

Vulnerability description

We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.

Risk description

There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.

Recommendation

We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.

Classification

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.malak.com.pk	TXT	Text record	"v=DMARC1;p=quarantine;rua=mailto:aqif@eleganzluxury.com;"

Vulnerability description

We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.

Risk description

Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.

Recommendation

We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.malak.com.pk	TXT	Text record	"v=DMARC1;p=quarantine;rua=mailto:aqif@eleganzluxury.com;"

Vulnerability description

We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.

Risk description

Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.

Recommendation

To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.

Evidence

Software / Version	Category
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Operating System	Accuracy
Crestron XPanel control system	92%

Evidence

DKIM selector	Key type	Key size	Value
key	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwP8vNDXaZCBDx+5bU7jkWSUBUi/N5HpA/jFy3Ttuzj3VQdxbAFLgVas21e75KzYM0FsgqYf0770ei4A6woQF7s2t0XsyvDPdwhAlzrxsxMLbpjnRIDz7BP1kpAPZ1kjM1be+/xj0lqYZPXZm1ObzuKGFtgSLEDGB+iAm3kAkygh3E0V6RUXYNaQldP+KcBezQ" "ZloZQ60DyMj6JivbikNc3B33jQ/f6odAwwThlIQYzN3V/b5vjQb/LcPjFqMPKj3vvkc4EugYUxvRWIl54M6sOhGEot3L3yi6fwH9c1aVd8MDCHjT2a4UoYQjIdCwHoLdONrpfFHkQorB4qv+afp4wIDAQAB"

Evidence

Software / Version	Category
Shopify	Ecommerce
Cart Functionality	Ecommerce
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Bogos	Shopify apps
Secomapp	Shopify apps
PayPal	Payment processors
jsDelivr	CDN
Glider.js	JavaScript libraries
PushOwl	Marketing automation
lit-html 3.3.3	JavaScript libraries
lit-element 4.2.2	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Facebook Pixel 2.9.349	Analytics
core-js 3.37.0	JavaScript libraries
Priority Hints	Performance
Preact	JavaScript libraries
DoubleClick Floodlight	Advertising
HSTS	Security
Cloudflare	CDN
Open Graph	Miscellaneous
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Domain Queried	DNS Record Type	Description	Value
malak.com.pk	SPF	Sender Policy Framework	"v=spf1 ip4:65.108.5.107 include:spf.protection.outlook.com -all"

Evidence

Domain Queried	DNS Record Type	Description	Value
malak.com.pk	A	IPv4 address	104.21.57.30
malak.com.pk	A	IPv4 address	172.67.188.233
malak.com.pk	NS	Name server	dolly.ns.cloudflare.com
malak.com.pk	NS	Name server	paul.ns.cloudflare.com
malak.com.pk	MX	Mail server	0 malak-com-pk.mail.protection.outlook.com
malak.com.pk	SOA	Start of Authority	dolly.ns.cloudflare.com. dns.cloudflare.com. 2408498740 10000 2400 604800 1800
malak.com.pk	AAAA	IPv6 address	2606:4700:3033::6815:391e
malak.com.pk	AAAA	IPv6 address	2606:4700:3035::ac43:bce9
malak.com.pk	TXT	Text record	"MS=ms74631044"
malak.com.pk	SPF	Sender Policy Framework	"v=spf1 ip4:65.108.5.107 include:spf.protection.outlook.com -all"
_dmarc.malak.com.pk	TXT	Text record	"v=DMARC1;p=quarantine;rua=mailto:aqif@eleganzluxury.com;"

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.