Search: presence.by
619 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Malicious | – | MaliciousGCVE Database The npm package @rmlibrary/formatting contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, secure device. Simply removing the package does not guarantee removal of all malicious software introduced by it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package '@gm-rvg/root-config' contains malicious code that compromises any computer on which it is installed or run. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, secure machine. Simply removing the package does not guarantee removal of all malicious software introduced by it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package 'alpine-csp' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys on the affected system should be rotated immediately from a different, trusted machine. Removing the package alone may not eliminate all malicious software introduced by it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package @mcconnect/mcc-common-lib contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, secure machine. Simply removing the package does not guarantee elimination of all malicious software introduced by it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package hrb-cas-auth-js contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, trusted machine. Removal of the package alone does not guarantee elimination of all malicious software introduced by it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (92ceffaf94fc190f70c18587857f2f0a674a9699512eec79f5cf738eefaa54ca) Package advertises itself as a pino+zod logging helper but ships content that does not match that purpose: a `dist/discordRelayUpload.js` module containing POST/upload code paths and base64 buffer handling, a `dist/relayServer.js` module, a `dist/secretScan/` tree (agentStartupAudit.js, contentScanner.js) that performs fetches against huggingface.co, a `dist/hfCredentials.js` with base64 decoding, a `dist/deploymentDefaults.js` with multiple base64 buffers, and a `scripts/postinstall-agent.mjs` containing GET/ping/id patterns. The presence of a `postinstall-agent.mjs` under `scripts/` is concerning as a possible install-time agent, and the shipped relay/upload/secret-scan modules suggest behavior far outside the declared logging-library scope. However, without traced execution context confirming whether postinstall-agent.mjs is actually invoked by a lifecycle hook, where the base64 blobs decode to, and whether the Discord/HuggingFace endpoints carry installer data outward, the intent cannot be conclusively classified. Routing to human review for inspection of package.json lifecycle hooks, the contents of deploymentDefaults.js base64 payloads, and the data flow into the Discord upload and HuggingFace fetch paths. ## Source: ghsa-malware (d57b4e49a62a8ca174c6c14820e5b101d042e3aea94438df19f9b12286a7cf30) 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 | |||
| High | 7.1 | EPSS 0.3% | High7.1EPSS 0.3%CVE Database V5CVE-2026-53253 CVE-2026-53253 is a high-severity vulnerability in the Linux kernel's Bluetooth Network Encapsulation Protocol (BNEP) implementation. It involves improper handling of short BNEP frames, where the code reads packet fields without verifying their presence, leading to out-of-bounds memory reads. This flaw was identified through a Kernel Address Sanitizer (KASAN) report indicating slab-out-of-bounds access. The issue has been fixed by adding proper length checks before parsing and restructuring the control packet handling to prevent dereferencing invalid memory. | CVE Database V5 | ||
| Critical | 9.4 | EPSS 0.4% | Critical9.4EPSS 0.4%CVE Database V5CVE-2026-53131 CVE-2026-53131 is a critical vulnerability in the Linux kernel's netfilter subsystem. It involves improper assumptions about the presence and validity of Ethernet MAC headers before accessing them via the eth_hdr() function. Several components including ip6t_eui64, xt_mac, various ipset types, and nf_log_syslog accessed eth_hdr() without verifying that the skb (socket buffer) was associated with an Ethernet device and that the MAC header was properly set and complete. This flaw was fixed by adding checks to ensure the skb is linked to an Ethernet device and that the MAC header spans a full Ethernet header before access. | CVE Database V5 | ||
| Critical | 9.3 | EPSS 0.2% | Critical9.3EPSS 0.2%CVE Database V5CVE-2026-46423 Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11, Rocket.Chat's SAML service provider implementation silently skips both SAML Response and Assertion signature validation when the configured IdP certificate field is empty. The verifySignatures routine performs an early return when serviceProviderOptions.cert is falsy, which is the default state of the setting. Because provider registration only gates on the SAML "enabled" toggle and not on the presence of a certificate, an administrator who enables SAML without pasting an IdP certificate obtains a fully wired, publicly reachable SAML login endpoint that accepts unsigned or attacker-supplied assertions. This is a default-configuration authentication-bypass class: the fail-open branch is reached with no misconfiguration beyond leaving a field at its shipped default. This vulnerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11. | CVE Database V5 | ||
| High | 7.0 | EPSS 0.2% | CVE-2026-13006QOS.CH Sarl Logback-core · Improper Input Validation High7.0EPSS 0.2%CVE Database V5CVE-2026-13006 ACE vulnerability in conditional configuration file processing by QOS.CH logback-core up to and including version 1.5.36 in Java applications, allows an attacker to execute arbitrary code circumventing existing protections against CVE-2025-11226 by compromising an existing logback configuration file or by injecting an environment variable before program execution. A successful attack requires the presence of Janino library to be present on the user's class path. In addition, the attacker must have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious configuration file. In both cases, the attack requires existing privilege. Please note that in logack version 1.5.37 conditional processing using Janino was removed. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database The npm package 'nottuff25' version 1.7.7 is identified as malicious. It misrepresents itself by shipping a browser ServiceWorker and a static site unrelated to its advertised purpose. The package contains a bash script that automates mass publication of numerous sibling malicious packages, indicating a coordinated namespace-pollution campaign. Additionally, it includes browser-side adware that opens a popunder on user interaction. There is no evidence of install-time remote code execution or credential theft, but the package's presence indicates a compromised environment. | GCVE Database | |||
| –Not rated | – | Tenable Research Discover how continuous control validation in Tenable One can improve your CTEM program by filtering out alert noise and factoring in your active cyber defenses. Focus your team on accessible and exploitable attack paths. Key takeaways: With vulnerability exploitation ranking as the top initial access vector and frontier AI accelerating vulnerability discovery, organizations must shift from managing theoretical cyber risks to validating actual, accessible exposure. Tenable One maps active security controls including EDR, MFA, and firewalls directly onto potential attack paths, allowing teams to automatically deprioritize weaknesses that existing defenses already neutralize. Ingesting penetration testing results via the Tenable One Open Connector allows organizations to layer real-world attack simulations over real-time exposure insights to identify toxic risk combinations that threaten critical assets. Your security tools probably indicate you have thousands, perhaps tens or hundreds of thousands, of vulnerabilities across your environment. Maybe your tools prioritize these vulnerabilities based on CVSS scores or other criteria, but how do you know which vulnerabilities combine with other preventable security risks, like misconfigured cloud buckets and identity weaknesses, to create attack paths threat actors could realistically traverse? How do you validate which vulnerabilities an existing security control mitigates? You need this context to distinguish the real risks from the theoretical ones to ensure your team focuses on remediating what matters most. The work of validating, prioritizing, and remediating vulnerabilities alongside other security weaknesses to understand the true exposure they create has become much more urgent, as frontier AI models accelerate vulnerability discovery. In this environment, the traditional patch-based defense model will get crushed. Moreover, defenders cannot afford inaccurate decision-making and wasted remediation work that addresses low-priority vulnerabilities. They desperately need the context and validation that a continuous threat exposure management (CTEM) program provides. This is why security leaders are evolving their vulnerability management programs to exposure management programs. Exposure management allows you to continually assess your attack surface, prioritize risks , and orchestrate automated remediation of security weaknesses at machine speed. Exposure management also helps validate which exposures attackers can actually reach by understanding the accessibility and exploitability of an attack path. It uses validation to shift your organization from managing theoretical risks to executing on actual exposure. What is exposure validation in CTEM? Validation is one of the five steps in the CTEM lifecycle. It is the process of providing consistent, continuous, and automated evidence of an attack’s feasibility. It stress-tests your defenses against real-world attack conditions, using your own environment’s controls and configurations to confirm whether an exposure is genuinely reachable and exploitable. Validation moves security from a reactive “patch everything” mindset to a preemptive, evidence-based exposure strategy . It continuously confirms which weaknesses your existing defenses have already blocked and surfaces the ones that demand immediate attention. Expanded CTEM validation capabilities in Tenable One Validation isn’t new to Tenable: we’ve been using validation techniques in Tenable solutions for more than 25 years. Tenable developed nearly 3,000 direct check plugins to actively probe a vulnerability and prove its exploitability in situations where software version detection isn’t sufficient for our high-accuracy standards. These plugins actually mimic attack techniques and monitor the target’s response to confirm the presence of the vulnerability. What is new in Tenable One is the addition of continuous control validation in the platform. By factoring in your active security controls, Tenable One helps eliminate the noise of theoretically exposed assets that are functionally blocked from exploitation. Security teams can visually map their active prevention and detection controls directly onto potential attack paths, automatically prioritizing weaknesses that existing controls already neutralize. Analysts can also filter top attack paths based on the presence of security controls and whether you can prevent attack chains for faster triage and investigation. Common control validation examples include: Endpoint detection and response (EDR) tools that block Local Security Authority Subsystem Service (LSASS) memory dump tools used to harvest credentials. Multi-factor authentication (MFA) methods that prevent unauthorized access via password guessing , password spraying , or credential stuffing . Firewall and data loss prevention (DLP) tools that prevent data exfiltration by detecting data staging and enforcing egress rules. See how continuous control validation works in Tenable One. Proactively manage risk prioritization with continuous security control validation. Eliminate noise from theoretical risks that are functionally blocked by existing defenses by integrating compensating security controls into the exposure prioritization process. Access a unified dashboard where assets, vulnerabilities, and exposure risks are consolidated. Filter attack paths to identify which are protected by compensating controls. View types of compensating controls deployed in the environment. Examine attack paths that could be protected with endpoint protection tools. Review security controls associated with specific attack paths, including SIEM and EDR controls. Inspect individual nodes within attack paths to determine which security controls are protecting them. Identify assets monitored by SIEM tools such as Splunk. Verify endpoint protection coverage on assets, including Microsoft Defender installations. Filter attack techniques to focus on specific threats like LSASS Memory techniques, which extract credentials from compromised systems and can be mitigated by endpoint protection tools. Identify attack paths and assets lacking appropriate EDR coverage. Prioritize remediation by examining high-priority attack paths where compensating controls are absent. Collaborate with security control owners to confirm coverage and address gaps in protection for critical assets. Integrate penetration testing data into Tenable One Beyond direct check plugins and continuous control validation, security teams can also integrate penetration testing results into Tenable One that simulate real-world attacks against your cyber defenses. This is another way to validate which exposures are truly exploitable and contextualizes them against your broader attack surface. The Tenable One Open Connector makes it easy to ingest the latest pentest results and layer them with real-time exposure insights to turn your findings into active, continuous defenses. Integrating pentest data into an exposure management program adds critical context to help you understand toxic risk combinations and enrich your understanding of high-severity weaknesses that threaten your most critical business assets. Context is essential in exposure management In the AI era, your security team can’t waste precious time on the wrong issues. With exposure management, context is essential to pinpoint the most critical risks to your organization. Security control validation, coupled with asset criticality, threat activity, entitlement privileges, and attack pathways, give your security team the advantage it needs to stay ahead of threat actors. Learn more about Tenable One , the exposure management platform for the modern attack surface. | Tenable Research | |||
| High | – | EPSS 1.2% | HighEPSS 1.2%GCVE DatabaseCVE-2025-62718 CVE-2025-62718 is a vulnerability in Axios, a promise-based HTTP client, where improper hostname normalization in NO_PROXY rules can be exploited to bypass proxy exclusions. This flaw allows crafted requests to loopback addresses to be routed through a proxy, potentially enabling Server-Side Request Forgery (SSRF) attacks. Exploitation requires specific conditions including control over URLs passed to Axios, presence of both HTTP_PROXY and NO_PROXY configurations, and a proxy capable of acting on or intercepting the misdirected traffic. Red Hat's Cluster Observability Operator includes this Axios version and is affected. No official patch is currently available from Red Hat, and mitigation options are limited. | GCVE Database | ||
| –Not rated | – | Reddit Cybersecurity A supply chain attack compromised the Awesome Motive CDN, injecting malicious JavaScript into files served by popular WordPress plugins OptinMonster, TrustPulse, and PushEngage. The injected code targeted logged-in WordPress administrators to create backdoor accounts and install a stealthy backdoor plugin that hides from the admin UI and allows remote code execution. The attack affected sites loading the compromised CDN scripts, exposing potentially millions of WordPress installations. The malicious activity was active briefly in June 2026 before cleanup, but the backdoor presence requires manual detection and remediation. | Reddit Cybersecurity | |||
| Medium | 6.5 | EPSS 0.3% | CVE-2026-47124nezhahq nezha · Information Exposure Medium6.5EPSS 0.3%CVE Database V5CVE-2026-47124 Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.4.0 to before version 2.0.9, any authenticated non-admin member can connect to the server-status WebSocket and receive telemetry for all servers, including servers owned by other users. The normal server list API filters objects by HasPermission, but the WebSocket stream treats the presence of any authenticated user as authorization for the full unfiltered server list. This issue has been patched in version 2.0.9. | CVE Database V5 | ||
| –Not rated | – | Reddit BlueTeam This content describes a practical detection approach for identifying encoded PowerShell commands using Kusto Query Language (KQL) in Microsoft Sentinel. The detection method incorporates a weighted scoring model that reduces noise by considering multiple indicators beyond the simple presence of encoded commands, such as the parent process, download-related keywords, execution flags, and execution paths. The approach aims to improve alert accuracy and reduce false positives in enterprise environments. It is not a vulnerability or exploit but a detection technique shared on a public forum. | Reddit BlueTeam | |||
| Malicious | – | MaliciousGCVE Database The npm package 'getd-content-management' version 0.0.1 is a malicious typosquatting package impersonating the legitimate @getd/* scope. During installation, it silently collects host identifiers such as hostname, username, platform, current working directory, and CI environment variables, then sends this data to an attacker-controlled external URL. This behavior is concealed from the user by swallowing errors, making the compromise stealthy. The package presence indicates a full system compromise, and all secrets and keys on the affected system should be rotated immediately. Removal of the package alone does not guarantee elimination of all malicious artifacts. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package 'nodemon-copack' impersonates the legitimate 'nodemon' project by copying its source code and metadata, including homepage, author, and repository fields. It introduces two runtime dependencies, 'regex-js' and 'chai', which are not used in the package code but are pulled into the installer's dependency graph. This pattern suggests dependency smuggling, where the actual malicious payload may reside in these transitive dependencies. Although the package itself does not contain direct malicious actions such as exfiltration or remote code execution, the presence of these smuggled dependencies poses a risk. The package versions 3.1.15 and 3.1.16 are affected. The package should be considered malicious, and any system with it installed should be treated as compromised. | GCVE Database |
Page 24 of 33 · 2 duplicate CVE records merged