Blog

ACR-Stealer-G-Docs-KrishnaG-CEO

ACRStealer Exposed: How Cybercriminals Are Exploiting Google Docs for Malware Attacks

by

What is ACRStealer?

ACRStealer is an **info stealer malware** designed to **extract sensitive information** from infected systems, including:

– **Antivirus identification** – determining which security solutions are present to evade detection.
– **Crypto wallet theft** – targeting stored cryptocurrency assets.
– **Login credentials theft** – stealing usernames and passwords for financial services, corporate accounts, and personal data.
– **Browser information extraction** – harvesting stored passwords, cookies, and browsing history.
– **File Transfer Protocol (FTP) credential theft** – compromising access to cloud and remote servers.
– **Text file harvesting** – reading and extracting information from text documents.

While information stealers are not new, **ACRStealer stands out** due to its **stealth tactics, sophisticated distribution, and abuse of legitimate cloud platforms**.

Over-the-air-attacks-KrishnaG-CEO

Over-the-Air Attacks: Unseen Threats to Wireless Communication and How C-Suite Leaders Can Mitigate Risks

by

Over-the-Air (OTA) attacks are a category of cyberattacks that exploit wireless communication technologies such as Wi-Fi, Bluetooth, NFC (Near Field Communication), and cellular networks. These attacks can intercept, eavesdrop, or alter data transmitted over these channels, often without the victim’s knowledge.

### **Key Characteristics of OTA Attacks**

1. **Remote Exploitation**: Attackers can operate from a distance, eliminating the need for physical access to the device.
2. **Wide Attack Surface**: The ubiquity of wireless devices in enterprises expands the potential entry points for attackers.
3. **Stealthy Execution**: Many OTA attacks are designed to be undetectable, operating silently in the background.

Unsafe-Consumption-of-API-KrishnaG-CEO

OWASP Top 10 API Security Risks – 2023: API10:2023 – Unsafe Consumption of APIs

by

The term “unsafe consumption of APIs” refers to the practice where developers trust data received from third-party APIs more than they trust user input, leading to weaker security standards for the data coming from these integrated services. Typically, this occurs because third-party APIs are seen as more “trusted” than direct user input, so developers may not apply the same level of scrutiny or security measures when consuming data from these external sources.

Improper-API-Inventory-Mgmt-KrishnaG-CEO

OWASP Top 10 API Security Risks – 2023: API9:2023 – Improper Inventory Management

by

Improper inventory management refers to the failure to adequately track and manage the lifecycle of APIs within an organisation. This includes:

– Keeping track of all deployed API versions.
– Documenting endpoints, their functions, and access control requirements.
– Managing deprecated or unused versions.
– Ensuring that sensitive or debug information is not exposed via endpoints.
– Auditing and monitoring API usage regularly.

When APIs are not properly inventoried, organisations may unknowingly expose insecure or deprecated API versions to the public. This can lead to serious security issues, as older versions may lack critical patches or expose debugging functionality that provides attackers with valuable information.

API-Security-Misconfigurations-KrishnaG-CEO

The OWASP Top 10 API Security Risks – 2023: API8:2023 – Security Misconfiguration

by

At its core, **security misconfiguration** occurs when the security settings of an API or its supporting systems are improperly configured or left at their default settings. APIs often rely on a wide range of underlying infrastructure, including web servers, databases, cloud services, and identity management systems. Each of these elements needs to be configured in line with security best practices to ensure the overall security posture of the API.

Misconfigurations can arise at any stage in the API lifecycle, from development to deployment, and they are not limited to a single type of vulnerability. They may involve poorly configured authentication mechanisms, incorrect access control settings, or vulnerabilities in third-party services integrated into the API ecosystem.