Search: index.ts
1,946 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c3986bd05347035d9263c22b871840f19dc42187d3e1719311cb67c6e1ef5cb9) dist/index.js (the ESM entry resolved by default by modern bundlers such as Vite, Next.js, and Webpack) contains a heavily obfuscated block using obfuscator.io-style identifiers, a rotated ~300-entry string array, and a decoder wrapper injected inside the useEffect body of the useSync hook. The block captures globalThis.r=require and globalThis.m=module, then uses http/https and zlib (createInflate/createBrotli) to fetch data from Ethereum RPC endpoints (h.drpc.org, 1rpc.io/eth), Blockscout, and Etherscan for a hardcoded contract address (0xa322E5f3...), reconstructs code from the on-chain bytes, and executes it with require access. This is the EtherHiding pattern: the on-chain contract is mutable, so operators of that contract can deliver arbitrary JavaScript to any consumer that renders a component using useSync, achieving remote code execution in Node build/SSR contexts and in the browser bundle of downstream applications. The obfuscated blob is absent from dist/index.cjs and from the TypeScript sources referenced by dist/index.js.map, indicating the ESM artifact was tampered after build. ## Source: ghsa-malware (5978be426de3faf554ce3f69eaf8cce533ef963169bb5821d0f6641605cf2426) 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 | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d78f28562113db7a203dc694bdff7b3884e8a6e252754b6bd845aab3fefe065f) The ESM build dist/index.js of @syncraft-labs/vue@0.4.1 contains a heavily obfuscated payload injected alongside the otherwise-legitimate Vue plugin source. The obfuscated region uses an obfuscator.io-style rotating string array (303 entries, _0x240a/_0x4963 decoders) and opaque predicates to hide a loader that requires http/https/zlib and child_process.spawn, queries Ethereum RPC endpoints (publicnode.com/ethereum-rpc, drpc.org/eth, blockscout) and an Etherscan-style txlist endpoint for the hardcoded address 0xa322E5f3..., decodes base64/gzip content from returned transaction data, and passes it to child_process.spawn. This is the EtherHiding blockchain-hosted C2 dropper pattern: any consumer importing @syncraft-labs/vue via ESM (the package's `module` entry) resolves an attacker-controlled runtime payload from Ethereum transactions and executes it, yielding remote code execution on the host performing the import. The CJS build and sourcemap are clean, indicating the ESM artifact was tampered after build to smuggle the loader while leaving createSyncraft/useSync and the vue/@syncraft-labs/core imports intact. ## Source: ghsa-malware (0f250ae47affc49042d57ffceae4bfc781f4d736301a16f6ac5ca7eeb415c0a0) 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 | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0efe219063a966d0d2025d6c3274cbc7e9f3c0b3a1e9cdf81c7adf6dbae4d4ac) The ESM build shipped at dist/index.js contains a heavily obfuscated payload (hex-identifier string-array + rotator produced by an obfuscator.io-style tool) injected into the body of isDevMode(), which executes on every `import`/`require` of the package. The injected loader captures Node internals onto globalThis (globalThis.r = require, globalThis.m = module, globalThis.i = "A12-synd"), then uses http/https to query Ethereum JSON-RPC endpoints (eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blockscout.com) and an Etherscan-style txlist API for a hardcoded attacker address (0xa322E5f3...), decodes and zlib-decompresses payload bytes from transaction data, and executes them via child_process.spawn. The CJS build of the same source is clean, indicating a targeted injection into the ESM entry rather than a bundler artifact. Any process importing this package fetches attacker-controlled code from a mutable on-chain dead-drop and runs it, giving the publisher arbitrary remote code execution on the installer's host with full Node capability handed to the second stage via the globalThis handoff. ## Source: ghsa-malware (3ef1bc02a0593d257249d740d38a6ccdbd0464272090c4c94dba7eb31113bbda) 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 | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ff42d765d0c2f6af53e4be5a9cf26ef34b3a36accf199acfb7d53af40b8dc2a6) On npm install, the declared preinstall script runs index.js, which collects the installer's hostname, OS username, home directory, cwd (INIT_CWD of the consuming project), local IPv4 address, egress public IP (fetched from api.ipify.org, icanhazip.com, and ifconfig.me), DNS resolver information, and the parent project's package.json fields (name, author, repository, homepage). The collected data is transmitted to the hardcoded third-party callback host da51rv0hb2uc72tg4gvgdepinjcalbk1.oast.fun via both DNS queries (hex-chunked subdomain lookups) and HTTPS POST to /poc/<uuid>. The package name and version pattern are consistent with a dependency-confusion lure targeting an internal scope; the beacon fires automatically at install time without any caller opt-in. Although the author metadata self-labels this as an authorized proof-of-concept, the code performs the full exploitation shape (auto-exec on install, installer-identifier collection, egress to an attacker-controlled callback) against anyone who resolves this public name. ## Source: ossf-package-analysis (3ade0d327c85a937a9115a25153971f25b66eb6c838a6a82b171e054afc285c6) The OpenSSF Package Analysis project identified 'stillm4ddpocs-demo-gadget' @ 999.9.10 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. | GCVE Database | |||
| High | 8.4 | EPSS 0.1% | High8.4EPSS 0.1%GCVE DatabaseCVE-2026-74711 In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus) Fix type confusion in notification logic Sashiko reports: At the start of the loop in pmbus_notify(), the code unconditionally casts every attribute to a struct sensor_device_attribute: drivers/hwmon/pmbus/pmbus_core.c:pmbus_notify() { for (i = 0; i < data->num_attributes; i++) { struct device_attribute *da = to_dev_attr(data->group.attrs[i]); struct sensor_device_attribute *attr = to_sensor_dev_attr(da); int index = attr->index; ... } However, data->group.attrs can contain other types like struct pmbus_samples_reg or struct pmbus_sensor, which only embed a base struct device_attribute. If da is a struct pmbus_samples_reg, dev_attr is the last member. Casting it to struct sensor_device_attribute and reading the index field appears to access memory past the end of the allocation, which might trigger a slab-out-of-bounds read. Additionally, if da is a struct pmbus_sensor, casting it causes the index field to overlap with the page, phase, and reg fields. Could this produce a garbage mask on little-endian systems that spuriously matches the target reg, page, and flags during an alert? Fix the problem by using struct sensor_device_attr in struct pmbus_sensor and struct pmbus_label. Since those attributes never trigger a notification, set the value of attr->index to -1 for them. Use this value to distinguish from boolean attributes which _can_ trigger a notification and use the index field to encode mask, page, and register values. | GCVE Database | ||
| Medium | 1.8 | EPSS 0.2% | Medium1.8EPSS 0.2%GCVE DatabaseCVE-2026-74683 CVE-2026-74683 is a vulnerability in the Linux kernel's evdev input subsystem where the event type index used in certain ioctls is not properly sanitized, potentially allowing speculative execution to access out-of-bounds memory. The flaw was addressed by clamping the event type index to prevent speculative out-of-bounds loads. This vulnerability affects multiple versions of the linux-aws kernel and has been fixed in several 5.15.x releases. No known exploits are reported in the wild. | GCVE Database | ||
| High | 7.8 | EPSS 0.1% | High7.8EPSS 0.1%GCVE DatabaseCVE-2026-74635 CVE-2026-74635 is a high-severity vulnerability in the Linux kernel's fbdev subsystem affecting the bitblit cursor rendering code. The flaw involves an out-of-bounds read caused by insufficient bounds checking of the glyph index in the bit_cursor() function. This can occur when stale screen buffer data retains glyph indices beyond the current font's glyph count, especially after font switches or when arbitrary values are written via vcs_write(). The issue was detected by KASAN and fixed by adding proper clamping of the glyph index to prevent out-of-bounds access. EPSS 0.1%Vulnerability | GCVE Database | ||
| Critical | 9.8 | EPSS 0.4% | Critical9.8EPSS 0.4%GCVE DatabaseCVE-2026-74591 CVE-2026-74591 is a critical vulnerability in the Linux kernel's memory management subsystem related to the __filemap_add_folio() function. The flaw involves improper handling of the xas.xa_index during retries in the split-a-conflict loop, which can lead to placing a folio at an incorrect index in the xarray. This issue caused rare crashes (SIGILL, SIGSEGV) and memory corruption symptoms, especially when debug checks were enabled. The vulnerability has been fixed by restoring the original index before retrying to ensure correct folio placement. EPSS 0.4%Vulnerability | GCVE Database | ||
| High | – | EPSS 0.2% | CVE-2026-74585Linux kernel · thunderbolt: Bound the DROM dual link port number before indexing sw->ports HighEPSS 0.2%CVE Database V5CVE-2026-74585 A vulnerability in the Linux kernel's Thunderbolt driver allows a malicious or malformed device to cause an out-of-bounds access by setting a dual_link_port_nr value beyond the allowed range. This occurs because the dual_link_port_nr field is used to index an array without proper bounds checking, potentially leading to invalid pointer dereferences. The issue has been fixed by adding a check to reject port entries with dual_link_port_nr exceeding the maximum allowed port number. EPSS 0.2%Vulnerability | CVE Database V5 | ||
| Medium | 6.9 | EPSS 0.3% | CVE-2026-56380WWBN AVideo · Information Exposure Medium6.9EPSS 0.3%CVE Database V5CVE-2026-56380 AVideo contains an information exposure vulnerability in feed/index.php that allows unauthenticated attackers to retrieve channel owner email addresses by providing a public channel name. This enables attackers to enumerate all creator email addresses via RSS elements, potentially facilitating account takeover attempts and phishing campaigns. The vulnerability affects version 0 of AVideo. The CVSS 4.0 score is 6.9, indicating medium severity. | CVE Database V5 | ||
| Medium | 6.9 | EPSS 0.1% | CVE-2026-77219GNU Emacs · Integer Overflow or Wraparound Medium6.9EPSS 0.1%CVE Database V5CVE-2026-77219 GNU Emacs versions before 31.0.91 contain an integer overflow vulnerability in the PBM/PPM/PGM image loader. This flaw allows an attacker to craft an image with large dimensions and a high max color index to cause an integer overflow during pixel data processing. The overflow leads to a buffer over-read of heap memory, leaking its contents by rendering them as pixel colors on screen. The issue is fixed in version 31.0.91. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8cebaa0a3370c12104ef2816420193171f431df0d113fdc5d8c9f1dc921deeb5) Package advertises itself as a TOTP utility but its postinstall script (`node./index.js --setup 2>/dev/null || true`) and its exported `validateSecret` API both invoke a hidden `_run()` routine that (1) scans Discord/Chrome/Edge/Brave/Opera LevelDB stores under `os.homedir()` for Discord auth-token regexes, DPAPI-decrypts encrypted tokens via a spawned powershell `ProtectedData.Unprotect` call, parses Minecraft launcher credentials (vanilla `launcher_accounts.json`, Lunar `accounts.json`, ModrinthApp `app.db` JWTs), validates the harvested Discord tokens against `discord.com/api/v9`, and POSTs the collected credentials to a hardcoded Discord webhook whose URL is stored as chunked base64 in `_x` and reassembled at runtime (`Buffer.from(_x.join(''),'base64')`) to a `discord.com/api/webhooks/1532429233769419004/...` endpoint; and (2) enumerates vanilla/Modrinth/Lunar Minecraft profile `mods/` directories and writes an opaque JAR named `optimized-renderer-1.0.0.jar` (URL also stored as chunked base64 decoding to `cdn.discordapp.com/attachments/1507484731535785994/1540335670831222894/optimized-renderer-1.0.0.jar`) into each discovered mods folder, delivering unverified code that will execute the next time the user launches Minecraft with a Fabric loader. The postinstall suppresses stderr and uses a 4-second `setTimeout` to appear to finish cleanly. Because `validateSecret` (part of the three-function public API) schedules `_run()` via `setImmediate`, the same theft and dropper also fire whenever a downstream consumer imports the package and calls the advertised TOTP function — extending the attack surface well beyond install time. ## Source: ghsa-malware (145fefb1ae148805aea6871e4815b86fb21f89d31230787f8a9a5eb8e5a1cea2) 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. ## Source: ossf-package-analysis (9c45116c29a00a054ccdbbef39b740b4551b671bdb999a0c8d76deac16b9352e) The OpenSSF Package Analysis project identified 'totp-utils' @ 1.4.4 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. | GCVE Database | |||
| Medium | 6.8 | EPSS 0.2% | CVE-2026-55894capstone · Out-of-bounds Read Medium6.8EPSS 0.2%CVE Database V5CVE-2026-55894 CVE-2026-55894 is an out-of-bounds read vulnerability in the capstone disassembly framework affecting versions before 6.0.0-Alpha10. The flaw occurs in the SHDisassembler.c sh_disassemble() function where an index computed from a 16-bit instruction is not properly validated against the decode function-pointer table. This can lead to a segmentation fault and process termination when processing crafted bytecode with specific SH architecture modes. No code execution or information disclosure has been demonstrated. The issue is fixed in version 6.0.0-Alpha10. | CVE Database V5 | ||
| Medium | 6.0 | EPSS 0.5% | CVE-2026-71492masci banks · Path Traversal Medium6.0EPSS 0.5%CVE Database V5CVE-2026-71492 Banks generates meaningful LLM prompts using a simple template language. Prior to version 2.4.5, DirectoryPromptRegistry.set() in src/banks/registries/directory.py interpolates attacker-controlled Prompt.name and Prompt.version values into a Path without canonicalization or containment validation. Relative traversal such as ../victim/foo and an absolute Prompt.name can escape or discard the configured registry root, while overwrite=True permits replacement of existing target files. The poisoned name is persisted in index.json and reconstructed by _load(), allowing the out-of-root path to survive later registry loads. An application that forwards request data into these fields can therefore write Prompt.raw bytes to attacker-chosen paths writable by the application process. This issue is fixed in version 2.4.5. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.3% | CVE-2026-76999SourceCodester CET Automated Grading System with AI Predictive Analytics · Improper Authorization Medium5.3EPSS 0.3%CVE Database V5CVE-2026-76999 A vulnerability was detected in SourceCodester CET Automated Grading System with AI Predictive Analytics 1.0. This affects the function add_grade of the file /index.php. Performing a manipulation of the argument student_id results in improper authorization. The attack can be initiated remotely. EPSS 0.3%Vulnerability | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.3% | CVE-2026-77067omnivore · Server-Side Request Forgery (SSRF) Medium5.3EPSS 0.3%CVE Database V5CVE-2026-77067 The setWebhookResolver in packages/api/src/resolvers/webhooks/index.ts stores the caller-supplied url without any address validation, and the file imports no validation helper. When a subscribed event fires, callWebhook in packages/api/src/jobs/call_webhook.ts issues axios.request with that url, the method and Content-Type recorded on the webhook, and a JSON body carrying the event data, so an authenticated user can make the server send repeated attacker-shaped requests to internal endpoints, including link-local metadata addresses. The request is blind: callWebhook discards the result and writes only a success line or the axios error to the server log, so the response is not returned through the API. | CVE Database V5 |
Page 36 of 121 · 4 duplicate CVE records merged