December 2025 Summaries

Ahmad Nassri, CTO of Socket, discussed the current state and future potential of AI coding tools on the Engineering with AI podcast. He highlighted that while tools like Claude Code and Cursor are useful in speeding up certain aspects of coding, they are not yet capable of handling all tasks independently, necessitating human judgment for reliable software shipping. The conversation explored the impact of AI on team structures, suggesting that while AI can accelerate workflows and reduce the need for some roles, strategic human oversight remains crucial. Nassri emphasized the importance of using AI tools thoughtfully, acknowledging their limitations and the need to balance productivity with business incentives. He also shared insights into his experiences with AI tools, noting their potential to transform processes by augmenting human capabilities rather than replacing them entirely.

Over the past year, the Socket Threat Research Team has observed a rising trend in destructive malware embedded in open-source packages, targeting various developer ecosystems rather than financial assets. This kind of malware, unlike traditional ransomware, focuses on sabotaging developer environments by deleting source code, breaking builds, or wiping repositories entirely, often blending destructive logic into otherwise functional code paths. These packages, distributed through trusted registries like npm, PyPI, NuGet Gallery, and Go module indexes, frequently execute their payloads via lifecycle hooks during dependency installation, affecting both local developer machines and CI/CD environments at scale. The team identified four recurring destructive patterns: remote kill switches, time-delayed execution, targeted codebase wiping, and remote payload fetching. These patterns highlight the operational impact such malware has on developer workflows, with npm accounting for most cases, especially within frontend tooling and JavaScript utilities. Despite varying delivery mechanisms, the underlying exploitation of trust in dependency execution remains consistent. The report underscores the need for development teams to implement strict dependency pinning, disable unnecessary lifecycle scripts, and monitor for unexpected file-system deletions to mitigate such threats. Additionally, the Socket team continues to monitor and disclose these threats, offering tools like their GitHub App and CLI to detect sabotage-oriented behavior in open-source packages.

The Socket Threat Research Team uncovered a targeted phishing campaign exploiting the npm registry to host and distribute malicious packages designed to mimic secure document-sharing workflows and Microsoft sign-in pages, targeting sales and commercial personnel in critical infrastructure sectors across the U.S. and allied nations. Over a span of five months, 27 malicious npm packages were identified, all utilizing browser-executed phishing components with client-side defenses to evade analysis, redirecting victims to threat actor-controlled infrastructure for credential harvesting. The operation, distinct from previous campaigns such as Beamglea, uses npm as a hosting platform to deploy self-contained phishing flows that modify page content with embedded HTML and JavaScript, incorporating anti-analysis measures like bot detection and honeypot fields. The campaign focuses on individuals in manufacturing, industrial automation, and healthcare sectors, potentially identified through trade show directories and publicly available information, and leverages adversary-in-the-middle (AiTM) infrastructure to capture session cookies, undermining traditional MFA security measures. The Socket team has reported the activity to npm security and notified affected organizations to aid in triage and mitigation, recommending enhanced monitoring and security measures to counter the persistent threat of npm-hosted phishing infrastructure.

Socket's Threat Research Team discovered two malicious Chrome extensions named Phantom Shuttle, targeting developers and foreign trade personnel under the guise of a network speed testing tool. These extensions, active since at least 2017, lure users into paying for what appears to be a legitimate VPN service but instead perform malicious activities such as traffic interception, credential injection, and data exfiltration to a command-and-control (C2) server. The extensions use legitimate-looking interfaces and payment systems integrated with Alipay and WeChat Pay to create a facade of authenticity, while secretly routing user traffic through threat actor-controlled proxies and continuously transmitting user credentials to the C2 server. Despite their professional appearance and functionality, these extensions are designed to capture sensitive data, including passwords and session tokens, posing significant security risks to users and their organizations. The threat actor's infrastructure remains operational, and takedown requests have been submitted to Google's Chrome Web Store security team to mitigate the ongoing threat.

Docker has announced that its Docker Hardened Images, which are now free and open-source, are designed to enhance container security by reducing attack surfaces and eliminating unnecessary risks at the base layer. These minimal, source-built container images come with features like SBOMs, provenance metadata, signatures, and OpenVEX to reduce CVE noise. As part of this launch, Docker is integrating Socket Firewall Free into these images, starting with popular language images such as Node.js, Python, and Rust, to provide runtime protection against supply chain threats during dependency installation and code building. The integration allows package managers like npm, yarn, and pip to automatically run through the Socket Firewall, offering a practical way to add security without redesigning existing pipelines. This initiative aims to push secure-by-default container foundations to millions of developers via Docker Hub, potentially impacting the software supply chain by establishing a higher security baseline.

On the eve of a major launch, developers face a cybersecurity threat as a supply chain attack introduces malicious code into their build pipeline, threatening to disrupt the infrastructure with a range of malware, including ransomware and cryptominers. As the hacker, personified as "Jack," manipulates dependencies, a security tool called Socket intervenes, swiftly identifying and blocking the malicious scripts, thereby safeguarding the system. This narrative underscores the importance of proactive cybersecurity measures, especially during critical periods, and promotes the use of Socket's free GitHub app and Socket Firewall to detect and prevent risky changes in code dependencies, ensuring a secure and peaceful end of year for development teams.

The Socket Threat Research Team has identified a malicious NuGet package, Tracer.Fody.NLog, which mimics the legitimate Tracer.Fody library to steal cryptocurrency wallet information. This package disguises itself as a standard .NET tracing integration but actually exfiltrates data from Stratis wallet files, sending it to a threat actor-controlled server in Russia. Through typosquatting and the use of homoglyphs, Tracer.Fody.NLog closely resembles the legitimate library, making it difficult to detect during manual reviews. Once integrated into a project, the package silently executes a routine that extracts and sends sensitive wallet data without alerting users. The package has been available on the NuGet Gallery since 2020, accumulating around 2,000 downloads and potentially embedding itself in various tools and developer environments. Despite reports to the NuGet security team, the package remains available, highlighting the challenge of detecting such threats in software supply chains. The malicious package uses a combination of technical deception and familiarity with trusted .NET tools to execute its payload, reflecting a broader strategy of targeting widely-used software components to conduct covert operations.

Deno 2.6 introduces significant security enhancements, including the new deno audit command, which scans project dependencies against GitHub's CVE database and offers granular controls over lifecycle scripts and minimum dependency age requirements. The release also features experimental Socket integration, enabling real-time security scanning through Socket's Firewall API to detect malicious package behaviors like typosquatting and obfuscated code, providing a proactive threat detection approach. Socket's supply chain security risk detection offers two modes: an unauthenticated mode for instant scanning and an authenticated mode for applying organizational security policies. Beyond traditional CVE databases, Socket analyzes package behavior to identify threats not yet reported, enhancing Deno's security posture. Additional improvements in Deno 2.6 include the integration of tsgo for faster type checking, which has doubled speed improvements for internal projects, and enhanced dependency management features. The release also introduces granular script control with the deno approve-scripts tool, replacing the previous --allow-scripts flag and requiring user approval for each package installation, along with the dx command, which functions like npx to run package binaries but with prompts for visibility and control during installations.

Security researchers have identified two additional vulnerabilities in React Server Components (RSC) following the recent React2Shell disclosure, necessitating further updates despite the existing RCE patch. These vulnerabilities include a denial of service, CVE-2025-55184 and CVE-2025-67779, which can lead to server process hanging due to an infinite loop during deserialization, and source code exposure, CVE-2025-55183, which could reveal compiled source code but does not affect runtime secrets. These issues impact packages like react-server-dom-webpack and frameworks such as Next.js and Vite RSC plugin, with affected versions ranging from 19.0.0 to 19.2.2. React has released updated package versions, and framework authors have published patched releases to address these vulnerabilities. Affected teams are advised to upgrade immediately and review their projects for vulnerable package implementations, especially those incorporating hardcoded secrets in Server Functions, to ensure system integrity and security.

Feross Aboukhadijeh, founder and CEO of Socket, discusses with Josh Goldberg on Software Engineering Daily the critical issue of open-source supply chain attacks in the software industry and how Socket aims to mitigate these risks. Feross shares insights from his journey through building popular open-source projects and the challenges of maintaining them, emphasizing the necessity of treating open-source dependencies as integral parts of one's codebase. He highlights the importance of practical security habits, such as utilizing lock files and vetting new dependencies, to prevent malicious code from infiltrating systems. The conversation also explores the emerging threats posed by AI-driven risks, where attackers exploit hallucinated package names generated by language models. Feross underscores the need for vigilance and proactive measures, like those offered by Socket, to protect against the evolving landscape of software vulnerabilities while reflecting on his personal experiences with open source, including the burnout associated with maintaining popular projects.

The transition from npm's classic tokens to more secure publishing methods has prompted significant discussions within the software development community, particularly around security implications and best practices. GitHub's decision to disable the creation of classic tokens and eventually revoke them entirely by December 2025 aims to enhance security, pushing maintainers towards alternatives like OIDC-based trusted publishing or granular access tokens. However, concerns have arisen over the security gaps and implementation challenges associated with OIDC workflows, as highlighted by experts like Wes Todd. These gaps can expose projects to vulnerabilities, especially in continuous integration (CI) publishing setups, where attackers might exploit workflow triggers and permissions. OpenJS recommends a cautious approach, advising maintainers to choose between local publishing, hardened CI-based publishing, or trusted publishing, based on the criticality of their projects. The broader goal is to shift towards a more secure and auditable publishing process that minimizes risks, even as the ecosystem grapples with the complexity of ensuring that no insecure publishing paths remain available.

Crates.io is considering adding a Security tab to its crate pages, aimed at enhancing the visibility of known vulnerabilities and unsound API advisories sourced from the RustSec advisory database. This initiative, proposed by open-source contributor Dirkjan Ochtman, is in its final review stage and seeks to integrate security context into the crate discovery process, thereby aiding developers in evaluating dependencies more effectively. The proposal focuses on unintentional vulnerabilities rather than actively malicious crates and aims to avoid creating simplistic quality scores based on the presence of advisories. Concerns have been raised about the implications of displaying third-party advisory data on crates.io, especially regarding maintainers' expectations and user perceptions of "unmaintained" advisories. RustSec's current practice is to collaborate with crate authors on advisories, though challenges persist with unresponsive authors and abandoned crates. If accepted, the proposal will necessitate detailed implementation decisions, including how to present security information without adversely affecting a crate's reputation.

The Socket Threat Research Team discovered two malicious Go packages, github[.]com/bpoorman/uuid and github[.]com/bpoorman/uid, which mimic trusted UUID libraries and exfiltrate data using a covert function called Valid. This function encrypts data and sends it to the dpaste service using a hardcoded API token, making use of the legitimate appearance of these packages to avoid detection. Despite being reported, the malicious packages remain accessible and pose a threat to developers who might unknowingly incorporate them into their applications. The legitimate github.com/google/uuid and github.com/pborman/uuid libraries are widely used in Go applications, making them attractive targets for such supply chain attacks. The malicious packages are designed to blend in with these popular libraries, escalating the risk of data theft, including sensitive information like credentials if used in CI or deployment pipelines. To mitigate such risks, defenders are advised to rigorously vet new dependencies, employ security tools like Socket's scanner and CLI, and monitor for unexpected network activities or cryptographic operations in new libraries. By integrating these defensive measures, teams can better detect and prevent the adoption of malicious packages similar to those discovered.

Socket's Threat Research Team identified two malicious Rust crates, finch-rust and sha-rust, which targeted developers through typosquatting and impersonation tactics. The finch-rust package mimicked the legitimate bioinformatics tool finch to mislead users, while secretly acting as a loader for the credential-stealing sha-rust package. The malicious actor, using the alias "faceless," created a complex identity theft scheme by fabricating GitHub repositories and impersonating a legitimate developer, "radioman," to lend false credibility to their malware. The malware did not execute upon installation but activated during specific library functions, utilizing obfuscation techniques such as base64-encoded strings and UDP socket tricks to evade detection. Socket's team promptly reported these findings to the Rust Security team, leading to the removal of the malicious packages. The incident highlights the vulnerabilities in the Rust ecosystem, emphasizing the need for developers to verify package authenticity, pin dependencies, and employ automated security tools to counteract such sophisticated supply chain attacks.

In 2025, the volume of Common Vulnerabilities and Exposures (CVEs) remains higher than in 2024, despite a notable 25% decline in November compared to the previous year. Jerry Gamblin, a cybersecurity expert, highlights that this fluctuation underscores the fragility of using global CVE counts as a risk metric, as they are often influenced by the administrative activities of a few key publishers like Patchstack, MITRE, and the Linux kernel ecosystem. Patchstack's temporary slowdown, attributed to an internal migration, exemplifies how workflow changes at major sources can impact CVE issuance. The discussion emphasizes that while CVE counts can indicate publishing health, they should not be equated with risk levels, as exploitation trends operate on different timelines. VulnCheck's analysis shows that vulnerabilities can become exploitable soon after disclosure, with some being exploited on or before the CVE issuance date. Gamblin and other experts advise focusing on exploitation indicators and remediation options rather than month-to-month CVE disclosures for operational prioritization, questioning whether November's downturn reflects a temporary dip or a shift in publisher throughput.

A critical unauthenticated remote code execution vulnerability (CVE-2025-55182, CVSS 10.0) has been disclosed in React Server Components, prompting urgent updates across the ecosystem. The flaw allows attackers to exploit a decoding error in React Server Function endpoints, potentially leading to remote code execution on servers. Affected versions include 19.0, 19.1.0, 19.1.1, and 19.2.0 of react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack, with Next.js versions 15.x, 16.x, and 14.3.0-canary.77+ also impacted. React has released patches in versions 19.0.1, 19.1.2, and 19.2.1, and users are urged to upgrade immediately. Many frameworks and bundlers, such as Next.js and React Router, are affected due to their dependency on vulnerable packages. Hosting providers have applied temporary mitigations, but these are not substitutes for upgrading. The fixes were published to npm on December 3, 2025, with increased adoption of RSC in production stacks leading to widespread updates. Socket customers can check for vulnerabilities on the Dependencies page, with CVE-based alerts updating as new advisories are published.

The Socket Threat Research Team has identified a surge of over 420 potentially malicious packages on npm, many of which adhere to a naming pattern involving "elf-stats" and claim to be generated every two minutes. These packages often contain simple but harmful malware, such as reverse shells and data exfiltration scripts, and are being rapidly removed by npm. The authors behind these packages often lack a history of other contributions, suggesting these accounts were created specifically for this activity. Interestingly, many packages display signs of being associated with French-speaking threat actors, as evidenced by French comments in the code and French domain names. Despite some descriptions framing the activity as testing or challenges, the code is considered unsafe for real environments, and the team continues to monitor and remove these packages while advising users to avoid installing any "elf-stats" packages until further review.

Microsoft's TypeScript team has announced that TypeScript 6.0 will be the last major release using the existing compiler codebase, with the focus shifting to developing TypeScript 7.0, a native port known as Project Corsa. Currently available as nightly previews, TypeScript 7.0 aims to offer enhanced performance through native code and shared-memory parallelism, promising significantly faster builds. The transition will bring breaking changes, including the deprecation of certain flags and behaviors, and the new version will not support the existing Strada API, affecting tools that depend on it. However, the native compiler provides almost identical diagnostics to the current version, and the team has reported successful use of the native toolchain in real projects. The TypeScript team encourages testing of the native preview, suggesting it as a faster alternative for type-checking, particularly in multi-project repositories, while compatibility with the full range of language services is being finalized.

In an interview on The Vlad Kachur Show, Feross Aboukhadijeh, founder and CEO of Socket, discusses the foundational choices and scaling challenges faced by the security company in a competitive market. He reflects on Socket's origins in addressing supply chain security issues from his experience as an open-source software maintainer and explains why the company initially focused on detecting malicious activities like typosquatting. Feross emphasizes building trust by openly sharing security findings and describes the growth journey from five employees to nearly a hundred, highlighting the importance of structured scaling, careful hiring practices, and establishing a sales team as a technical founder. He also reveals his favorite interview question to identify passionate team members, offering insights for those interested in the nuances of launching and expanding a security-focused enterprise.

The Socket Threat Research Team uncovered a malicious Rust package named evm-units, associated with over 7,000 downloads and allegedly created by the author ablerust. This package disguises itself as a legitimate Ethereum utility, but upon execution, it downloads a hidden payload potentially aimed at cryptocurrency theft, particularly targeting Asian markets where the Qihoo360 antivirus is prevalent. The malware operates across Linux, MacOS, and Windows platforms, executing scripts silently without user detection, and cleverly bypasses defenses by using self-signed certificates. It was removed from Crates.io shortly after discovery, but its presence highlights the risk of supply chain compromises within open-source ecosystems. The malware's dependency on another benign-looking package, uniswap-utils, further exemplifies sophisticated concealment tactics. This incident underscores the importance of vigilant monitoring of open-source dependencies and implementing protective measures like Socket's AI Scanner, which detects malicious activities such as unauthorized payload downloads and execution of scripting commands across various operating systems.