Author: blogmirnet

The Cybersecurity and Infrastructure Security Agency (CISA) released this Alert to provide guidance in response to a widespread software supply chain compromise involving the world’s largest JavaScript registry, npmjs.com. A self-replicating worm—publicly known as Shai-Hulud—has compromised over 500 packages.

After gaining initial access, the malicious cyber actor deployed malware that scanned the environment for sensitive credentials. The cyber actor then targeted GitHub Personal Access Tokens (PATs) and application programming interface (API) keys for cloud services, including Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.

The malware then:

Exfiltrated the harvested credentials to an endpoint controlled by the actor. Uploaded the credentials to a public repository named Shai-Hulud via the GitHub/user/repos API. Leveraged an automated process to rapidly spread by authenticating to the npm registry as the compromised developer, injecting code into other packages, and publishing compromised versions to the registry.

CISA urges organizations to implement the recommendations found in the alert to detect and remediate this compromise.

The following resources provide additional guidance on this compromise:

GitHub: Our plan for a more secure npm supply chain Palo Alto Networks Unit 42: Shai-Hulud Worm Compromises npm Ecosystem in Supply Chain Attack (Updated September 18) Socket: Updated and Ongoing Supply Chain Attack Targets CrowdStrike npm Packages ReversingLabs: Malware found on npm infecting local package with reverse shell

The 2025 NY Metro Joint Cyber Security Conference is in the planning stage, celebrating our 12th year featuring keynotes, panels and sessions aimed at educating everyone on the various aspects of information security and technology. Workshops featuring in-depth extended classroom-style educational courses to expand your knowledge and foster security discussions will take place virtually post-conference. Call for speakers and sponsors in open. You can find out more at InfoSecurity.NYC

AS a Member of the advisory board I invite you to the Kentucky Cybersecurity and Forensics Conference (KCFC 2025), scheduled for Saturday, October 25, 2025, at Bluegrass Community and Technical College in Lexington, Kentucky.

KCFC brings together academia, industry, and government to collaborate in building awareness of cybersecurity and digital forensics. The conference provides a platform for professionals, educators, and students to exchange ideas, share research, and discuss the latest trends and challenges in cybersecurity.

Registration is now open at www.Ky-cfc.com. Please see our tentative agenda for this event.

We look forward to your participation in this important event and your contribution to advancing our shared mission of fostering a stronger and more secure digital environment.

We hope to see you there!

NIST has released the initial public draft (IPD) of Special Publication (SP) 1331, Quick-Start Guide for Using CSF 2.0 to Improve the Management of Emerging Cybersecurity Risks, for public comment. The document highlights the topic of emerging cybersecurity risks and explains how organizations can improve their ability to address such risks through existing practices within the cyber risk discipline in conjunction with the NIST Cybersecurity Framework (CSF) 2.0. The guide also emphasizes the importance of integrating these practices with organizational enterprise risk management (ERM) to proactively address emerging risks before they occur. 

The comment period is open through September 21, 2025, at 11:59 PM. Please send your feedback about this draft publication to csf@nist.gov.

This publication is the most recent in a portfolio of CSF 2.0 Quick-Start Guides released since February 26, 2024. These resources provide different audiences with tailored pathways into the CSF 2.0 and make the Framework easier to put into action. View all CSF 2.0 quick-start guides here. 

Read the Quick-Start Guide

NIST has published the final version of Special Publication (SP) 800-227, Recommendations for Key-Encapsulation Mechanisms. A key-encapsulation mechanism (KEM) is a set of algorithms that can be used by two parties under certain conditions to securely establish a shared secret key over a public channel. This publication describes the basic definitions, properties, and applications of KEMs and provides recommendations for implementing and using KEMs securely.

NIST greatly appreciates all the feedback and discussion and has incorporated several updates to SP 800-227 based on the comments received. The public comment period on the initial public draft (IPD) was open through March 7, 2025, and the feedback received is now linked from the SP 800-227 publication details. NIST also held a virtual Workshop on Guidance for KEMs on February 25-26, 2025, to gather additional input on SP 800-227. Presentations and the recording of the workshop are available on the event web page.

Read More

The NJCCIC has observed an increase in the distribution of infostealing malware. This type of malware is popular among threat actors because of the kind and amount of information it can exfiltrate. Infostealers often have capabilities that allow threat actors to retrieve credentials, financial information, personally identifiable information (PII), messages, emails, and browser data.  Some infostealers, like Amatera, have the capacity to run secondary payloads.

Several popular infostealers are sold as malware-as-a-service (MaaS). This type of malware lowers the barrier to entry into cybercrime for individuals with limited or no coding skills, as they can purchase it via subscription, and it often features user-friendly interfaces. Amatera Stealer, a rebrand of ACR Stealer, has been among the many forms of malware distributed through Click Fix/Clear Fake attacks. Despite law enforcement taking down the core infrastructure of Lumma Stealer in early 2025, threat actors have utilized GitHub comments to trick users into downloading the infostealer, often claiming to be a fix for an undisclosed issue.

Phishing continues to be a common method for tricking users into downloading infostealers. Both XLoader and DarkCloud conduct phishing campaigns that involve a compressed .rar file that, when extracted, downloads and installs malicious software. Some campaigns start with a downloader, such as GuLoader, which, once installed, initiates the download of more malware that it typically stores on Google Drive. A current campaign ends with the download of SnakeKeylogger.

Recommendations

Avoid clicking links and opening attachments in unsolicited emails. Confirm requests from senders via contact information obtained from verified and official sources. Users should only submit account credentials on official websites. Users are advised to only download applications and software from official sources. Maintain robust and up-to-date endpoint detection tools on every endpoint. Consider leveraging behavior-based detection tools rather than signature-based tools. If you suspect an account has been compromised, change the account’s password immediately and ensure MFA is enabled for all online accounts. Review the Don’t Take the Bait! Phishing and Other Social Engineering Attacks  NJCCIC product for more information on common phishing and social engineering attacks. Report other malicious cyber activity to the NJCCIC and the FBI’s IC3.

The NJCCIC observed a malware campaign sent to New Jersey State employees, purporting to be proof of payment. The malicious emails contain a ZIP file labeled “Proof Of payment.001” with a SHA-256 hash. The ZIP file appears legitimate but includes a Microsoft EXE file labeled “u1ugeglmfc8xvoc” that drops several files, including a PowerShell script.

According to VirusTotal , the malware likely belongs to the Krypt or Kryptik Trojan family. Besides malicious email attachments, Trojan infections can also occur by downloading and executing files from untrusted and unsafe websites. They can perform malicious activities on infected systems without the target’s knowledge, such as creating backdoors, establishing remote connections with command and control (C2) servers, maintaining persistence, and dropping other malware. Some can also target and capture keyboard input, such as account credentials, financial information, and other sensitive data.

In a similar campaign, researchers discovered phishing emails using malicious RAR attachments labeled “Proof of Payment.” If clicked, it launches the included VBE file using wscript[.]exe and drops several files, including a PowerShell script and a JPG file embedded with the DarkCloud stealer . If executed, DarkCloud uses process injection, outbound connections to suspicious top-level domains (TLDs), persistence, and data exfiltration. DarkCloud is programmed to steal account credentials from email and FTP clients and data from web browsers. The researchers observed an uptick in DarkCloud stealers targeting financial organizations in August 2025. These recent malware campaigns highlight the importance of awareness and strengthening defenses to help prevent threat actors from infecting systems and exfiltrating data to commit identity theft and financial fraud.

Recommendations

Refrain from responding to unsolicited communications, opening attachments, or clicking links from unknown senders. Exercise caution with communications from known senders. Confirm requests from senders via contact information obtained from verified and official sources. Download software or files only from reputable sources or websites. Use strong, unique passwords for all accounts and enable multi-factor authentication (MFA) where available, choosing authentication apps or hardware tokens over SMS text-based codes. Keep systems up to date and apply patches after appropriate testing. Run updated and reputable anti-virus or anti-malware programs. Report malicious cyber activity to the NJCCIC and the FBI’s IC3.

To help organizations protect their data against possible future attacks from quantum computers, the National Institute of Standards and Technology (NIST) has released a publication offering guidelines for implementing a class of post-quantum cryptography (PQC) algorithms known as key-encapsulation mechanisms, or KEMs.

A KEM is a set of algorithms that can be used by two parties to securely establish a shared secret key over a public channel — a sort of first handshake between parties that want to exchange confidential information. Recent examples of KEMs include ML-KEM and HQC.

The new publication, Recommendations for Key-Encapsulation Mechanisms (NIST Special Publication 800-227), describes the basic definitions, properties and applications of KEMs and provides recommendations for implementing and using KEMs securely.

The publication also offers guidelines for implementing “hybrid” setups that use both conventional and PQC algorithms together, requiring an attacker to break both. For those organizations that opt to use such hybrid setups during their transition to using PQC, the publication offers a way to implement them safely and securely.

The finalized publication reflects comments received on the initial public draft before the deadline on March 7, 2025, as well as input from NIST’s virtual Workshop on Guidance for KEMs held Feb. 25-26, 2025. Comments on the draft are available at the final version’s publication details. Presentations and the recording of the workshop are available on the event webpage.

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, threat actors could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

Threat Intelligence

Google is aware that an exploit for CVE-2025-10585 exists in the wild.

Systems Affected

Chrome prior to 140.0.7339.185/.186 for Windows Chrome prior to 140.0.7339.185 for Linux

Risk

Government: – Large and medium government entities: High – Small government entities: Medium

Businesses: – Large and medium business entities: High – Small business entities: Medium

Home Users: Low

Recommendations

Apply appropriate updates provided by Google to vulnerable systems immediately after appropriate testing. Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. Restrict execution of code to a virtual environment on or in transit to an endpoint system. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. Restrict use of certain websites, block downloads/attachments, block JavaScript, restrict browser extensions, etc. Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from untrusted sources. Remind users not to visit untrusted websites or follow links provided by unknown or untrusted sources.

References

Google: https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_17.html  CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-10500 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-10501 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-10502

A vulnerability has been discovered in WatchGuard Fireware OS, which could allow for arbitrary code execution. Fireware OS is the software that runs on WatchGuard Firebox firewalls. Fireware includes a Web UI that includes a way to manage, and monitor each Firebox in your network. Successful exploitation of this vulnerability may allow a remote unauthenticated attacker to execute arbitrary code. This vulnerability affects both the mobile user VPN with IKEv2 and the branch office VPN using IKEv2 when configured with a dynamic gateway peer. If the Firebox was previously configured with the mobile user VPN with IKEv2 or a branch office VPN using IKEv2 to a dynamic gateway peer, and both of those configurations have since been deleted, that Firebox may still be vulnerable if a branch office VPN to a static gateway peer is still configured.

THREAT INTELLIGENCE:
There are currently no reports of this vulnerability being exploited in the wild.

SYSTEMS AFFECTED:

• Fireware OS 11.10.2 up to and including 11.12.4_Update1
• Fireware OS 12.0 up to and including 12.11.3
• Fireware OS 2025.1

RISK:
Government:

• Large and medium government entities: High
• Small government entities: Medium

Businesses:

• Large and medium business entities: High
• Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:
A vulnerability has been discovered in WatchGuard Fireware OS, which could allow for arbitrary code execution. Details of the vulnerability are as follows:

Tactic: Initial Access (TA0001):
Technique: Exploit Public-Facing Application (T1190):

• An Out-of-bounds Write vulnerability in the WatchGuard Fireware OS iked process may allow a remote unauthenticated attacker to execute arbitrary code (CVE-2025-9242).

Successful exploitation of this vulnerability may allow a remote unauthenticated attacker to execute arbitrary code. This vulnerability affects both the mobile user VPN with IKEv2 and the branch office VPN using IKEv2 when configured with a dynamic gateway peer. If the Firebox was previously configured with the mobile user VPN with IKEv2 or a branch office VPN using IKEv2 to a dynamic gateway peer, and both of those configurations have since been deleted, that Firebox may still be vulnerable if a branch office VPN to a static gateway peer is still configured.

RECOMMENDATIONS:
We recommend the following actions be taken:

• Apply appropriate updates provided by WatchGuard to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
  • Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
  • Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
  • Safeguard 7.5 : Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
  • Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
  • Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
  • Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
  • Safeguard 18.2: Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
  • Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
  • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
  • Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
• Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
  • Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
• Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
  • Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
  • Safeguard 10.5:  Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

REFERENCES:

WatchGuard:
https://www.watchguard.com/wgrd-psirt/advisory/wgsa-2025-00015
 
CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-9242
 
Arctic Wolf:
https://arcticwolf.com/resources/blog/cve-2025-9242/