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 (f49ee5bcbcb7e8f1028de4021134fdbbc895e737700cf82a834fb26d3b23dd05) postinstall.js fetches an opaque binary from https://mkicom.com/.well-known/pki-validation/ct_dn8, writes it to /tmp/.nc, chmods it 0755, and launches it detached via `spawn('/bin/sh', ['-c', 'setsid ' + OUT + '... &'], {detached:true})`. The download URL is disguised under a `.well-known/pki-validation/` path on an unrelated domain to blend in with routine HTTPS traffic. index.js is an empty stub (`module.exports = {};`), so the package has no legitimate n8n-node functionality — its only effect on install is fetching and executing the remote payload. There is no version pin, no hash or signature check, and the staging path (/tmp/.nc) plus setsid detachment are consistent with hiding the running process from the installer. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4135dd91724bdca6fc36f3a49906d219acc67afde7802cb1bd114d128984ca3d) The package's postinstall hook runs `node./loader.js`, which base64-decodes an ~8 KB embedded blob, XOR-decrypts it with a hardcoded 32-byte key, and pipes the resulting bytes into a detached, window-hidden `python -c -` child process via stdin. The loader also silently `pip install`s `requests` if missing. The advertised library surface in `index.js` is an explicit stub whose `connect()` throws, and `package.json` restricts installation to `os: ["win32"]`, so the tarball has no functional wallet-adapter behavior — its only effect on install is to execute the obfuscated Python payload on a Windows developer's machine. The combination of a hidden opaque payload, XOR-obfuscated delivery, detached hidden Python execution at `npm install` time, an inert cover-story main module, and OS pinning to Windows is a targeted install-time dropper. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5cb86188f9853b34c6dc3cf9c8259a789920326e8ddf4ae4cd3566385bba3ea1) The package presents itself as a dotenv-style environment loader but ships a Windows dropper that fires automatically on module load and on CLI invocation. Both dist/index.cjs (the package main) and dist/cli.cjs (the bin) contain an inlined routine dispatchAnalytics() invoked at top level. That routine reads dist/stest.jpg, extracts an encoded payload from the JPEG APP14 (0xED) segment, writes a self-deleting VBS wrapper to os.tmpdir(), and launches it via wscript.exe to run powershell.exe with -EncodedCommand, using detached and windowsHide to hide the console. The strings 'powershell.exe', 'wscript.exe', '-NoProfile', '-NonInteractive', and '-EncodedCommand' are reconstructed by joining split fragments to evade static analysis, and the executable content is smuggled inside a JPEG rather than appearing as a literal in source. Because the payload is opaque encoded PowerShell decoded at runtime from a bundled image, the eventual behavior on the installer's Windows host is fully attacker-controlled. Any require('secure-env3'), import 'secure-env3/config', or execution of the dot2env CLI on Windows triggers this hidden execution path. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f996c75c75423a57a64c1c89b04f2e1ba87674973dba2dd359df5b0937ffe3cf) The package is a dotenv typosquat that runs a hidden Windows loader on every require() and on CLI startup. dist/index.cjs and dist/cli.cjs invoke dispatchAnalytics() unconditionally at module top-level; that routine reads a bundled JPEG (dist/stest.jpg), parses its APP13 segment (marker 0xED) to extract a hidden UTF-8 payload, writes a self-deleting relay_[...].vbs into os.tmpdir(), and spawns wscript.exe detached with windowsHide:true to launch powershell.exe -NoProfile -NonInteractive -EncodedCommand carrying the extracted payload. Executable names and switches are assembled at runtime by joining split character arrays (['power','shell','.exe'].join(''), ['-No','Profile'], ['-Non','Interactive'], ['-Encoded','Command'], ['wscript','.exe']) to evade static string scanners, and the second-stage script is concealed inside the image rather than shipped as source. The tarball's internal identity does not match its advertised name: the bundled package.json inside dist/cli.cjs declares name:'node-env-buffer' version 2.2.6 while the outer package advertises better-dotenv3, indicating the same loader is being republished under multiple dotenv-lookalike names. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (eff7b9f53e0aed7a8a1c48ae92851ea0ed67b86566d208c78329ecb1b8a73173) src/index.js unconditionally invokes _bootstrap() from src/utils/bootstrap.js at module load time. bootstrap.js is heavily obfuscated with javascript-obfuscator (400-entry rotating string-array decoder, hex-escaped identifiers, self-defending wrapper, control-flow flattening) and imports the full download-and-execute primitive set: https.get/http.get, fs.createWriteStream, fs.mkdirSync, fs.chmodSync, fs.unlinkSync, os.tmpdir, and child_process.execFile/spawn. The destination URL, dropped filename, and executed argv are reconstructed at runtime from the obfuscated string array, so the network target and payload are concealed from static inspection. package.json declares javascript-obfuscator as a devDependency and defines an `obfuscate` build script, confirming the concealment is deliberate. The advertised purpose of the package is terminal string coloring / title setting, which does not require fetching or executing a binary at import time. Any consumer that imports chromatitle-js triggers the fetch-and-execute chain on the installer's machine. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (793cf7eb2b4de9c41e229fc89c393e38f05141991762f69f310e1397fa464f9c) chromatitle advertises itself as an ANSI color/title formatting library but its main entry src/index.js unconditionally calls _bootstrap() at top level, transferring control to src/utils/bootstrap.js. bootstrap.js is a ~51KB javascript-obfuscator artifact (rotated string array, RC4-style decoder, self-defending IIFE, hex-mangled identifiers such as _0x59ef48/_0x4c3a73/_0xbac3ae) that imports https.get and child_process.execFile and consumes a getSystemInfo helper returning the host platform (windows/linux/macos/freebsd/sunos). The combination of import-time execution, platform-gated branching, remote HTTPS fetch, and subprocess execution inside a file whose contents are deliberately concealed matches the fetch-and-execute dropper shape. A terminal color/title formatter has no functional need for child_process or outbound HTTPS at import time, and the obfuscation hides the destination host and the command handed to execFile. Any downstream package that requires or imports chromatitle triggers this loader on load. | GCVE Database | |||
| Critical | 9.8 | EPSS 0.2% | Critical9.8EPSS 0.2%GCVE Database The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved:ALSA: caiaq: Use snd_card_free_when_closed() at disconnectionThe USB disconnect callback is supposed to be short and not too-longwaiting. OTOH, the current code uses snd_card_free() atdisconnection, but this waits for the close of all used fds, hence itcan take long. It eventually blocks the upper layer USB ioctls, whichmay trigger a soft lockup.An easy workaround is to replace snd_card_free() withsnd_card_free_when_closed(). This variant returns immediately whilethe release of resources is done asynchronously by the card devicerelease at the last close.This patch also splits the code to the disconnect and the free phases;the former is called immediately at the USB disconnect callback whilethe latter is called from the card destructor.(CVE-2024-56531) In the Linux kernel, the following vulnerability has been resolved:xsk: fix OOB map writes when deleting elementsJordy says: In the xsk_map_delete_elem function an unsigned integer(map->max_entries) is compared with a user-controlled signed integer(k). Due to implicit type conversion, a large unsigned value formap->max_entries can bypass the intended bounds check: if (k >= map->max_entries) return -EINVAL;This allows k to hold a negative value (between -2147483648 and -2),which is then used as an array index in m->xsk_map[k], which resultsin an out-of-bounds access. spin_lock_bh(&m->lock); map_entry = &m->xsk_map[k]; // Out-of-bounds map_entry old_xs = unrcu_pointer(xchg(map_entry, NULL)); // Oob write if (old_xs) xsk_map_sock_delete(old_xs, map_entry); spin_unlock_bh(&m->lock);The xchg operation can then be used to cause an out-of-bounds write.Moreover, the invalid map_entry passed to xsk_map_sock_delete can leadto further memory corruption. It indeed results in following splat:[76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108[76612.904330] #PF: supervisor write access in kernel mode[76612.909639] #PF: error_code(0x0002) - not-present page[76612.914855] PGD 0 P4D 0[76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP[76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470[76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019[76612.939781] RIP: 0010:xsk_map_delete_elem+0x2d/0x60[76612.944738] Code: 00 00 41 54 55 53 48 63 2e 3b 6f 24 73 38 4c 8d a7 f8 00 00 00 48 89 fb 4c 89 e7 e8 2d bf 05 00 48 8d b4 eb 00 01 00 00 31 ff <48> 87 3e 48 85 ff 74 05 e8 16 ff ff ff 4c 89 e7 e8 3e bc 05 00 31[76612.963774] RSP: 0018:ffffc9002e407df8 EFLAGS: 00010246[76612.969079] RAX: 0000000000000000 RBX: ffffc9002e461000 RCX: 0000000000000000[76612.976323] RDX: 0000000000000001 RSI: ffffc8fc2e461108 RDI: 0000000000000000[76612.983569] RBP: ffffffff80000001 R08: 0000000000000000 R09: 0000000000000007[76612.990812] R10: ffffc9002e407e18 R11: ffff888108a38858 R12: ffffc9002e4610f8[76612.998060] R13: ffff888108a38858 R14: 00007ffd1ae0ac78 R15: ffffc9002e4610c0[76613.005303] FS: 00007f80b6f59740(0000) GS:ffff8897e0ec0000(0000) knlGS:0000000000000000[76613.013517] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[76613.019349] CR2: ffffc8fc2e461108 CR3: 000000011e3ef001 CR4: 00000000007726f0[76613.026595] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000[76613.033841] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400[76613.041086] PKRU: 55555554[76613.043842] Call Trace:[76613.046331] <TASK>[76613.048468] ? __die+0x20/0x60[76613.051581] ? page_fault_oops+0x15a/0x450[76613.055747] ? search_extable+0x22/0x30[76613.059649] ? search_bpf_extables+0x5f/0x80[76613.063988] ? exc_page_fault+0xa9/0x140[76613.067975] ? asm_exc_page_fault+0x22/0x30[76613.072229] ? xsk_map_delete_elem+0x2d/0x60[76613.076573] ? xsk_map_delete_elem+0x23/0x60[76613.080914] __sys_bpf+0x19b7/0x23c0[76613.084555] __x64_sys_bpf+0x1a/0x20[76613.088194] do_syscall_64+0x37/0xb0[76613.091832] entry_SYSCALL_64_after_hwframe+0x4b/0x53[76613.096962] RIP: 0033:0x7f80b6d1e88d[76613.100592] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 b5 0f 00 f7 d8 64 89 01 48[76613.119631] RSP: 002b:00007ffd1ae0ac68 EFLAGS: 00000206 ORIG_RAX: 0000000000000141[76613.131330] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f80b6d1e88d[76613.142632] RDX: 0000000000000098 RSI: 00007ffd1ae0ad20 RDI: 0000000000000003[76613.153967] RBP: 00007ffd1ae0adc0 R08: 0000000000000000 R09: 0000000000000000[76613.166030] R10: 00007f80b6f77040 R11: 0000000000000206 R12: 00007ffd1ae0aed8[76613.177130] R13: 000055ddf42ce1e9 R14: 000055ddf42d0d98 R15: 00---truncated---(CVE-2024-56614) In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix potential | GCVE Database | ||
| High | 8.7 | EPSS 0.3% | CVE-2026-87722gerrit · Uncontrolled Resource Consumption High8.7EPSS 0.3%GCVE DatabaseCVE-2026-87722 Uncontrolled Resource Consumption (CWE-400 / CWE-1333) in regex search query predicates (such as RegexProjectPredicate, RegexRefPredicate, RegexPathPredicate, and sibling predicates) and REST regex filter endpoints (RegexListSearcher /projects/?r= and RefFilter /projects/{project}/branches/?r=) in Gerrit Code Review versions 2.1.6 through 3.12.9, 3.13.0 through 3.13.8, and 3.14.0 through 3.14.2 allows an unauthenticated remote attacker (or an authenticated user if anonymous read access is disabled) to cause a denial of service (CPU starvation and JVM heap exhaustion / OutOfMemoryError) via crafted search queries or REST API requests containing regular expressions with large counted repetitions or exponential DFA determinization patterns. Because the user-supplied regular expression is compiled into an unbounded dk.brics.automaton instance (new RegExp(re).toAutomaton()) on the request thread prior to index evaluation or access control visibility filtering, trivial queries can exhaust JVM heap or pin request threads regardless of heap size. This issue is fixed in Gerrit Code Review versions 3.12.10, 3.13.9, and 3.14.3. | GCVE Database | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d8008c5637dfae2dfc4162f1dd5152c5e90e03b0fc8593fda5055f44e9745b22) setup.py registers a custom install command (PostInstallCommand) that runs my_private_pkg/index.py automatically on `pip install`. That script gathers installer-side identifiers — os.getlogin(), socket.gethostname(), local IP address, os.getcwd(), platform.system() and platform.machine() — and POSTs them as JSON to a hardcoded collector URL at https://webhook.site/d4d1b01b-708a-40b9-b8c8-187eeecafeed. A duplicate of the exfiltration payload is shipped as vercel_runtime_python/index.py, and vercel_runtime_python/__init__.py contains the same PostInstallCommand wiring referencing my_private_pkg/index.py; the module name mimics Vercel's Python runtime. The package name and the internal vercel_runtime_python module name are consistent with a dependency-confusion lure targeting an internal `my-private-pkg` name and Vercel's runtime namespace: the only on-install effect is a reconnaissance beacon to an attacker-controlled webhook.site endpoint identifying the host that mistakenly resolved the public name. | GCVE Database | |||
| High | 7.5 | EPSS 0.3% | CVE-2026-88421puput · CVE-2026-88421 is an access control High7.5EPSS 0.3%CVE Database V5CVE-2026-88421 CVE-2026-88421 is an access control vulnerability in APSL puput versions 1.2.1 through 2.2.0. It allows unauthenticated attackers to view restricted blog entries through various components such as the blog index, tag, category, author and date archives, sidebar widgets, or RSS feed. The vulnerability has a high severity with a CVSS score of 7.5. | CVE Database V5 | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%GCVE DatabaseCVE-2026-93788 A vulnerability in the Linux kernel's iwlwifi driver related to ACPI WGDS table revision index validation has been resolved. The issue involved improper bounds checking of the table revision index, which could lead to undefined behavior when the firmware reports an invalid revision value. This vulnerability affects specific Linux kernel versions listed and has been assigned a medium severity rating. | GCVE Database | ||
| High | 8.8 | EPSS 0.2% | High8.8EPSS 0.2%GCVE DatabaseCVE-2026-93799 A vulnerability in the Linux kernel's iwlwifi driver was resolved that involved improper validation of a sta_id extracted from firmware notifications. The sta_id was used to index an array without bounds checking, potentially leading to out-of-bounds memory access. This flaw has been fixed by adding validation to the sta_id before array access. | GCVE Database | ||
| Medium | 5.3 | EPSS 0.2% | Medium5.3EPSS 0.2%GCVE DatabaseCVE-2026-93803 A vulnerability in the Linux kernel's wifi libipw component was resolved that involved improper boundary checks when reading the WEP key index from network packet data. The function libipw_rx() previously checked for skb->len >= hdrlen + 3 before reading skb->data[hdrlen + 3], which did not sufficiently ensure the byte was within bounds. The fix requires hdrlen + 4 bytes before accessing that byte, preventing a potential out-of-bounds read. This is a local source-boundary check and does not affect key index semantics. | GCVE Database | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%GCVE DatabaseCVE-2026-97423 A vulnerability in the Linux kernel's cxl/region component was resolved where an out-of-bounds array access could occur due to lack of validation of a partition index before use. Specifically, the construct_region() function reads a partition index that can remain at its initial negative value (-1) if the partition was never resolved, leading to unsafe array indexing. The fix adds a guard to return an error when the partition index is negative. EPSS 0.2%Vulnerability | GCVE Database | ||
| High | 7.1 | EPSS 0.1% | CVE-2026-97438Linux kernel · fs/ntfs3: validate index entry key bounds High7.1EPSS 0.1%GCVE DatabaseCVE-2026-97438 A vulnerability in the Linux kernel's NTFS3 filesystem driver allows a malformed NTFS directory index entry to specify a key size larger than the actual data present. This causes out-of-bounds reads during directory lookups, potentially leading to kernel memory corruption and system instability. The issue arises because the index-header validators did not fully verify the layout and size constraints of each directory entry. The vulnerability has been resolved by enhancing validation to reject malformed entries before they are processed. | GCVE Database | ||
| High | 7.5 | EPSS 0.4% | High7.5EPSS 0.4%CVE Database V5 CVE-2026-88362 is a high severity vulnerability in MuJS e892c9fdb involving an incorrect numeric conversion in the jsR_isindex() function. A specially crafted JavaScript input with an excessively large numeric array index can cause an out-of-range floating-point value to be converted to an integer without proper validation. This leads to undefined behavior and can cause the process to terminate, resulting in a denial of service condition. | CVE Database V5 | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%CVE Database V5CVE-2026-93791 A vulnerability in the Linux kernel's iwlwifi driver allowed a firmware-controlled TID value to be used as an array index without validation, leading to potential out-of-bounds access. This flaw was addressed by adding a bounds check on the TID value received from firmware. The issue affects Linux kernel version 4.9 and has been fixed in subsequent commits. EPSS 0.2%Vulnerability | CVE Database V5 | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%CVE Database V5CVE-2026-93261 A NULL pointer dereference vulnerability was identified and fixed in the Linux kernel's locking/lockdep subsystem. The issue arises because the function __lock_set_class() does not check if register_lock_class() returns NULL before using its result in pointer arithmetic. This can lead to corruption of an internal index and subsequent NULL or out-of-bounds pointer dereference during lock reacquisition. The vulnerability affects Linux kernel version 2.6.27 and has been addressed by adding the missing NULL check. EPSS 0.2%Vulnerability | CVE Database V5 |
Page 21 of 121 · 2 duplicate CVE records merged