SCA
Software composition analysis: vulnerable and malicious dependencies, supply chain, SBOMs.
- 8 last 24h
- 771 last 7 days
- 896 in view
- RSS
8 npm security advisories
GHSA-6crj-9fxx-v653: Malware in @leadstack/crm-connect
@leadstack/crm-connect = 1.0.15 → remove it
Why tagged?
- SCA from the title:
GHSA-6crj-9fxx-v653: Malware
- SCA from the title:
GHSA-hqfp-fhqg-4xc5: Malicious code in @leadstack/crm-connect (npm)
@leadstack/crm-connect = 1.0.15 → remove it | = 1.0.20 → remove it | = 1.0.30 → remove it | = 1.0.21 → remove it | = 1.0.19 → remove it | = 1.0.18 → remove it
Why tagged?
- SCA from the title:
GHSA-hqfp-fhqg-4xc5: Maliciou
- SCA from the title:
GHSA-p7r2-5ppv-hr6g: Malicious code in @c1-ease/core (npm)
@c1-ease/core = 3.0.0 → remove it | = 2.0.0 → remove it | = 1.0.0 → remove it | = 1.0.1 → remove it | = 99.0.1 → remove it | = 2.0.1 → remove it; +1 more
Why tagged?
- SCA from the title:
GHSA-p7r2-5ppv-hr6g: Maliciou
- SCA from the title:
GHSA-q599-9j7q-8xf5: Malicious code in @c1-ease/bank (npm)
@c1-ease/bank = 3.0.0 → remove it | = 1.0.0 → remove it | = 0.0.1 → remove it | = 2.0.0 → remove it | = 2.0.1 → remove it | = 1.0.1 → remove it; +1 more
Why tagged?
- SCA from the title:
GHSA-q599-9j7q-8xf5: Maliciou
- SCA from the title:
GHSA-69rf-36f8-r3fm: Malicious code in autoloan (npm)
autoloan = 3.0.0 → remove it | = 0.0.1 → remove it | = 2.0.0 → remove it | = 1.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-69rf-36f8-r3fm: Maliciou
- SCA from the title:
GHSA-v352-9p9c-2wv7: Malicious code in @c1-ease/autoloan (npm)
@c1-ease/autoloan = 1.1.0 → remove it | = 1.0.1 → remove it | = 1.0.0 → remove it | = 3.0.0 → remove it | = 2.0.0 → remove it | = 2.0.1 → remove it; +1 more
Why tagged?
- SCA from the title:
GHSA-v352-9p9c-2wv7: Maliciou
- SCA from the title:
GHSA-j5h6-446w-9q9c: Malicious code in @c1-ease/card (npm)
@c1-ease/card = 0.0.1 → remove it | = 99.0.1 → remove it | = 1.0.1 → remove it | = 1.1.0 → remove it | = 1.0.0 → remove it | = 2.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-j5h6-446w-9q9c: Maliciou
- SCA from the title:
GHSA-4w4w-phqm-jfpm: Malicious code in @c1-ease/commerce (npm)
@c1-ease/commerce = 2.0.1 → remove it | = 2.0.0 → remove it | = 3.0.0 → remove it | = 1.1.0 → remove it | = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-4w4w-phqm-jfpm: Maliciou
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
3 npm security advisories
GHSA-cxc9-87g6-qrj9: Malware in @wppconnect-team/wppconnect
@wppconnect-team/wppconnect = 2.4.1 → remove it
Why tagged?
- SCA from the title:
GHSA-cxc9-87g6-qrj9: Malware
- SCA from the title:
GHSA-pgrg-83q3-w7vr: Malicious code in aia-b-locator-fe (npm)
aia-b-locator-fe = 1.0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-pgrg-83q3-w7vr: Maliciou
- SCA from the title:
GHSA-r9wp-474x-c72c: Malware in @pkgship/frps-windows-amd64
@pkgship/frps-windows-amd64 = 0.71.1 → remove it
Why tagged?
- SCA from the title:
GHSA-r9wp-474x-c72c: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
3 PyPI security advisories
GHSA-w4wf-4398-p973: Malicious code in signed-manifest-guard (PyPI)
signed-manifest-guard = 0.1.7 → remove it
Why tagged?
- SCA from the title:
GHSA-w4wf-4398-p973: Maliciou
- SCA from the title:
GHSA-wqr9-48cj-55gj: Malicious code in instantscrape (PyPI)
instantscrape = 0.1.0 → remove it | = 0.1.5 → remove it | = 0.1.8 → remove it
Why tagged?
- SCA from the title:
GHSA-wqr9-48cj-55gj: Maliciou
- SCA from the title:
GHSA-23xm-8qc2-wp55: Malicious code in signed-manifest-updater (PyPI)
signed-manifest-updater = 0.1.5 → remove it
Why tagged?
- SCA from the title:
GHSA-23xm-8qc2-wp55: Maliciou
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
122 npm security advisories
GHSA-25qc-m4pw-2w8r / CVE-2026-122247: Budibase: Unauthenticated global-admin & database creation via tenant-confusion bypass of the one-time init guard (`POST /api/global/users/init`)
@budibase/server <= 3.38.1 → no fix
Why tagged?
- SCA from the title:
GHSA-25qc-m4pw-2w8r / CVE-202
- SCA from the title:
GHSA-r2q3-7m4h-63qg / CVE-2026-122244: Budibase: Cross-privilege Stored XSS in the Budibase Builder via broken HTML-escaping in `jsonFormatter.format()` rendered through `{@html}` in the CSP-less Builder origin
@budibase/server <= 3.38.1 → no fix
Why tagged?
- SCA from the title:
GHSA-r2q3-7m4h-63qg / CVE-202
- SCA from the title:
GHSA-xxqp-5qx8-gj5q / CVE-2026-63341: Aedes has Uncaught Exception and Uncontrolled Resource Consumption
aedes < 1.1.1 → 1.1.1
Why tagged?
- SCA from the title:
GHSA-xxqp-5qx8-gj5q / CVE-202
- SCA from the title:
GHSA-rf8v-v97c-32r7: Malware in orion-overlord
orion-overlord >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rf8v-v97c-32r7: Malware
- SCA from the title:
GHSA-wgw6-fp43-67xp: Malicious code in identity-poc (npm)
identity-poc = 1.0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-wgw6-fp43-67xp: Maliciou
- SCA from the title:
GHSA-j75q-4f87-cvr5: Malicious code in vreqtx-b5w3n-testmetest (npm)
vreqtx-b5w3n-testmetest = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-j75q-4f87-cvr5: Maliciou
- SCA from the title:
GHSA-8m2x-4x4x-cq8p: Malicious code in qzi2v-tttf1-testmetest (npm)
qzi2v-tttf1-testmetest = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-8m2x-4x4x-cq8p: Maliciou
- SCA from the title:
GHSA-f4pg-5677-5vm5: Malicious code in xssdoctor-muse-task448-provider-runtime (npm)
xssdoctor-muse-task448-provider-runtime = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-f4pg-5677-5vm5: Maliciou
- SCA from the title:
GHSA-4xj4-jwq4-jqwf: Malicious code in @kropa/baileys (npm)
@kropa/baileys = 1.0.0 → remove it | = 1.0.3 → remove it | = 1.0.2 → remove it | = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-4xj4-jwq4-jqwf: Maliciou
- SCA from the title:
GHSA-g4vg-qmwm-vh4c: Malicious code in @kropaku/baileys (npm)
@kropaku/baileys = 6.7.23 → remove it | = 6.7.22 → remove it | = 6.7.21 → remove it | = 6.7.24 → remove it | = 6.7.20 → remove it
Why tagged?
- SCA from the title:
GHSA-g4vg-qmwm-vh4c: Maliciou
- SCA from the title:
GHSA-v33p-qh9f-g4rp: Malicious code in @expo-probe-ff8e2b/snack-probe-c2a16 (npm)
@expo-probe-ff8e2b/snack-probe-c2a16 = 1.0.0 → remove it | = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-v33p-qh9f-g4rp: Maliciou
- SCA from the title:
GHSA-9v66-fc47-m28q: Malware in swaplearn-cli
swaplearn-cli >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9v66-fc47-m28q: Malware
- SCA from the title:
GHSA-2xxf-xq83-2h3q: Malware in @sapp1/baileys-pro
@sapp1/baileys-pro = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-2xxf-xq83-2h3q: Malware
- SCA from the title:
GHSA-7r7x-px4j-w4jg: Malware in dsh-blue-team-mode
dsh-blue-team-mode = 3.0.0-beta.18 → remove it | = 3.0.0-beta.17 → remove it | = 3.0.0-beta.20 → remove it
Why tagged?
- SCA from the title:
GHSA-7r7x-px4j-w4jg: Malware
- SCA from the title:
GHSA-v223-q8vf-c837: Malware in alwaysaqioo
alwaysaqioo = 1.1.1 → remove it | = 1.1.2 → remove it | = 1.1.3 → remove it | = 1.1.5 → remove it
Why tagged?
- SCA from the title:
GHSA-v223-q8vf-c837: Malware
- SCA from the title:
GHSA-24gg-4qq2-6r2g: Malware in tonty-tech-interviews
tonty-tech-interviews >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-24gg-4qq2-6r2g: Malware
- SCA from the title:
GHSA-wqcq-qg5g-jm7r: Malware in @zetagoaurum-socket/wasocket
@zetagoaurum-socket/wasocket = 2.1.0 → remove it | = 2.1.1 → remove it | = 2.1.2 → remove it | = 2.1.3 → remove it | = 2.1.4 → remove it | = 2.1.5 → remove it; +10 more
Why tagged?
- SCA from the title:
GHSA-wqcq-qg5g-jm7r: Malware
- SCA from the title:
GHSA-gjrr-f7w5-4j4g: Malware in @violetix/baileys
@violetix/baileys = 0.0.0-stage → remove it | = 0.3.18 → remove it | = 0.4.0 → remove it | = 0.5.0 → remove it | = 0.5.1 → remove it | = 0.5.2 → remove it; +7 more
Why tagged?
- SCA from the title:
GHSA-gjrr-f7w5-4j4g: Malware
- SCA from the title:
GHSA-94wh-c496-hm43: Malware in @basis-theory-elements/api-client
@basis-theory-elements/api-client >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-94wh-c496-hm43: Malware
- SCA from the title:
GHSA-5g25-2vc4-7gfh: Malware in @vanzky/baileys
@vanzky/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5g25-2vc4-7gfh: Malware
- SCA from the title:
GHSA-646c-v3qw-f7f9: Malware in @trashcore/baileys
@trashcore/baileys = 4.0.0 → remove it | = 4.0.1 → remove it | = 4.0.2 → remove it | = 4.0.5 → remove it | = 4.0.6 → remove it | = 4.0.7 → remove it; +20 more
Why tagged?
- SCA from the title:
GHSA-646c-v3qw-f7f9: Malware
- SCA from the title:
GHSA-w5w9-7whq-mg6h: Malware in @zanxiky/baileys
@zanxiky/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w5w9-7whq-mg6h: Malware
- SCA from the title:
GHSA-6fm5-pgx8-4crc: Malware in @yshtxxproject/baileys
@yshtxxproject/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6fm5-pgx8-4crc: Malware
- SCA from the title:
GHSA-w29j-8x2j-rrj6: Malware in @postman-cse/okta-aio-darwin-arm64
@postman-cse/okta-aio-darwin-arm64 = 0.8.10 → remove it | = 0.8.11 → remove it | = 0.9.0 → remove it | = 0.9.1 → remove it | = 0.10.0 → remove it | = 0.10.1 → remove it; +15 more
Why tagged?
- SCA from the title:
GHSA-w29j-8x2j-rrj6: Malware
- SCA from the title:
GHSA-f329-9g9w-rc6v: Malware in lyxe-baileys
lyxe-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f329-9g9w-rc6v: Malware
- SCA from the title:
GHSA-79f8-6qm5-fr58: Malware in @thepayulink/server
@thepayulink/server = 2.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-79f8-6qm5-fr58: Malware
- SCA from the title:
GHSA-9qcw-jqhm-rpg5: Malware in arshadahmed
arshadahmed = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-9qcw-jqhm-rpg5: Malware
- SCA from the title:
GHSA-3xvc-c2xw-876g: Malware in arifali
arifali = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-3xvc-c2xw-876g: Malware
- SCA from the title:
GHSA-m249-7c47-vgj8: Malware in apasih-me-polda
apasih-me-polda = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-m249-7c47-vgj8: Malware
- SCA from the title:
GHSA-qqvg-29x3-2xxq: Malware in apasih-ledong-po
apasih-ledong-po = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-qqvg-29x3-2xxq: Malware
- SCA from the title:
GHSA-3v73-9mj7-hjr2: Malware in apasih-ledan-puakfi
apasih-ledan-puakfi = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-3v73-9mj7-hjr2: Malware
- SCA from the title:
GHSA-9hx5-mqf4-wh7r: Malware in apasih-leda-pk
apasih-leda-pk = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-9hx5-mqf4-wh7r: Malware
- SCA from the title:
GHSA-w76f-qf34-79mp: Malware in apasih-led-pokiari
apasih-led-pokiari = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-w76f-qf34-79mp: Malware
- SCA from the title:
GHSA-cprp-4fgg-48m6: Malware in apakri
apakri = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-cprp-4fgg-48m6: Malware
- SCA from the title:
GHSA-f977-cj53-f9g2: Malware in antoniosouza
antoniosouza = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-f977-cj53-f9g2: Malware
- SCA from the title:
GHSA-83q9-4x8m-hmjj: Malware in anita-buy-mag
anita-buy-mag = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-83q9-4x8m-hmjj: Malware
- SCA from the title:
GHSA-w2jc-956j-48qw: Malware in anisyafira
anisyafira = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-w2jc-956j-48qw: Malware
- SCA from the title:
GHSA-fq86-p97c-8r66: Malware in animab
animab = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-fq86-p97c-8r66: Malware
- SCA from the title:
GHSA-mhwh-34xx-46j9: Malware in anidata-hopanud-mai
anidata-hopanud-mai = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-mhwh-34xx-46j9: Malware
- SCA from the title:
GHSA-4mq9-pj85-7r39: Malware in anidata-hd-madidsa
anidata-hd-madidsa = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-4mq9-pj85-7r39: Malware
- SCA from the title:
GHSA-mwj2-r2v8-vj88: Malware in anidata-haulid-mubda
anidata-haulid-mubda = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-mwj2-r2v8-vj88: Malware
- SCA from the title:
GHSA-cf7f-vc3h-26qp: Malware in ameliarichards
ameliarichards = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-cf7f-vc3h-26qp: Malware
- SCA from the title:
GHSA-3mc8-4chr-cc2r: Malware in ameliagordonlucaswalsh
ameliagordonlucaswalsh = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-3mc8-4chr-cc2r: Malware
- SCA from the title:
GHSA-gx8q-jq3c-79fr: Malware in ameerjamal
ameerjamal = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-gx8q-jq3c-79fr: Malware
- SCA from the title:
GHSA-fx2p-5qq8-2q73: Malware in alaaddindar
alaaddindar = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-fx2p-5qq8-2q73: Malware
- SCA from the title:
GHSA-x276-5hw5-w9q7: Malware in akifsaeed
akifsaeed = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-x276-5hw5-w9q7: Malware
- SCA from the title:
GHSA-f7pc-6mj6-3fvh: Malware in akanabi-alaigah-aimuava
akanabi-alaigah-aimuava = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-f7pc-6mj6-3fvh: Malware
- SCA from the title:
GHSA-9j29-6pq4-4x7g: Malware in akanabi-abia-baigbub
akanabi-abia-baigbub = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-9j29-6pq4-4x7g: Malware
- SCA from the title:
GHSA-cg75-5x4j-6x3m: Malware in akanabi-abia-babu
akanabi-abia-babu = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-cg75-5x4j-6x3m: Malware
- SCA from the title:
GHSA-8c8r-7wm8-rcwm: Malware in akabia-aligufi-av
akabia-aligufi-av = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-8c8r-7wm8-rcwm: Malware
- SCA from the title:
GHSA-495g-7fqv-pm25: Malware in ajmalzaki
ajmalzaki = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-495g-7fqv-pm25: Malware
- SCA from the title:
GHSA-h424-4vc8-w6f5: Malware in aiyuyia-iaydut-daina
aiyuyia-iaydut-daina = 1.1.2 → remove it
Why tagged?
- SCA from the title:
GHSA-h424-4vc8-w6f5: Malware
- SCA from the title:
GHSA-6q4g-3vrj-w5c6: Malware in aiboa-molipe-aramiia
aiboa-molipe-aramiia = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-6q4g-3vrj-w5c6: Malware
- SCA from the title:
GHSA-m5vg-59x6-6p6p: Malware in aiboa-milipe-apmuma
aiboa-milipe-apmuma = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-m5vg-59x6-6p6p: Malware
- SCA from the title:
GHSA-c8x2-qg96-2h24: Malware in anastasia-soluble-pot
anastasia-soluble-pot = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-c8x2-qg96-2h24: Malware
- SCA from the title:
GHSA-mw52-h95g-c4q2: Malware in analusia-aki-iniu
analusia-aki-iniu = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-mw52-h95g-c4q2: Malware
- SCA from the title:
GHSA-rwc7-j78x-qwgw: Malware in anala-akin-inuuli
anala-akin-inuuli = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-rwc7-j78x-qwgw: Malware
- SCA from the title:
GHSA-58cx-x5p7-642p: Malware in anala-akiman-inuli
anala-akiman-inuli = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-58cx-x5p7-642p: Malware
- SCA from the title:
GHSA-9435-p5jr-pvgh: Malware in anaisi-pafnolai-asigoga
anaisi-pafnolai-asigoga = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-9435-p5jr-pvgh: Malware
- SCA from the title:
GHSA-qj3g-mgf4-5mfx: Malware in anais-papoa-0pipaia
anais-papoa-0pipaia = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-qj3g-mgf4-5mfx: Malware
- SCA from the title:
GHSA-mvw4-7rfg-8c99: Malware in anabuyil-na0n-lukiahuas
anabuyil-na0n-lukiahuas = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-mvw4-7rfg-8c99: Malware
- SCA from the title:
GHSA-mvxr-rjfh-jxx6: Malware in anabuyil-na0n-luiahuas
anabuyil-na0n-luiahuas = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-mvxr-rjfh-jxx6: Malware
- SCA from the title:
GHSA-rg3w-v6c5-rp36: Malware in anabuyil-inupava-ninni
anabuyil-inupava-ninni = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-rg3w-v6c5-rp36: Malware
- SCA from the title:
GHSA-948f-976v-f4gw: Malware in anabuyil-inpa-ninni
anabuyil-inpa-ninni = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-948f-976v-f4gw: Malware
- SCA from the title:
GHSA-g3p9-hpj2-g74p: Malware in anabuyil-inanhu-ninni
anabuyil-inanhu-ninni = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-g3p9-hpj2-g74p: Malware
- SCA from the title:
GHSA-w4qw-m8x9-g8w5: Malware in anabuyi-inuba-ninni
anabuyi-inuba-ninni = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-w4qw-m8x9-g8w5: Malware
- SCA from the title:
GHSA-q6q4-4c8q-c88j: Malware in anabuyi-inu-ninni
anabuyi-inu-ninni = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-q6q4-4c8q-c88j: Malware
- SCA from the title:
GHSA-rxwc-4r9f-4jgv: Malware in amjadtaheem
amjadtaheem = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-rxwc-4r9f-4jgv: Malware
- SCA from the title:
GHSA-pfj7-pg2r-xpj8: Malware in amjadatef
amjadatef = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-pfj7-pg2r-xpj8: Malware
- SCA from the title:
GHSA-2r97-8h35-x4j8: Malware in aminchocolat
aminchocolat = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-2r97-8h35-x4j8: Malware
- SCA from the title:
GHSA-385h-j8j7-fx22: Malware in aciyuyia-iadut-daina
aciyuyia-iadut-daina = 1.1.2 → remove it
Why tagged?
- SCA from the title:
GHSA-385h-j8j7-fx22: Malware
- SCA from the title:
GHSA-v3cr-c366-8p7j: Malware in aciyudua-iadut-daina
aciyudua-iadut-daina = 1.1.2 → remove it
Why tagged?
- SCA from the title:
GHSA-v3cr-c366-8p7j: Malware
- SCA from the title:
GHSA-77f2-4wmf-rwgg: Malware in aciyua-iduat-doauuufa
aciyua-iduat-doauuufa = 1.1.2 → remove it
Why tagged?
- SCA from the title:
GHSA-77f2-4wmf-rwgg: Malware
- SCA from the title:
GHSA-vcx7-pfrh-mcfg / CVE-2026-115565: storyblok-backup: Stored path traversal via unsanitized Storyblok component names in backup output
storyblok-backup <= 0.7.0 → 0.7.1
Why tagged?
- SCA from the title:
GHSA-vcx7-pfrh-mcfg / CVE-202
- SCA from the title:
GHSA-3g82-77xr-68x5 / CVE-2026-63386: js-toml allows uncontrolled recursion in `load()` leading `RangeError` (stack exhaustion) on deeply nested input
js-toml < 1.1.3 → 1.1.3
Why tagged?
- SCA from the title:
GHSA-3g82-77xr-68x5 / CVE-202
- SCA from the title:
GHSA-jwgx-mp9m-jwcr / CVE-2026-58192: appium allows unauthenticated arbitrary file/directory deletion in @appium/storage-plugin
@appium/storage-plugin < 1.1.6 → 1.1.6
Why tagged?
- SCA from the title:
GHSA-jwgx-mp9m-jwcr / CVE-202
- SCA from the title:
GHSA-jcx6-j558-wppc: Malware in @metagl/sdk-render
@metagl/sdk-render = 4.0.6 → remove it
Why tagged?
- SCA from the title:
GHSA-jcx6-j558-wppc: Malware
- SCA from the title:
GHSA-xgr8-c5gp-x7xf: Malware in @corepassinc/remy-core-bin-win32-x64
@corepassinc/remy-core-bin-win32-x64 = 0.1.0-rc.30 → remove it
Why tagged?
- SCA from the title:
GHSA-xgr8-c5gp-x7xf: Malware
- SCA from the title:
GHSA-h82f-cjm4-g22r: Malware in @guicai777/mcp-doctor
@guicai777/mcp-doctor >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h82f-cjm4-g22r: Malware
- AI Security from the title:
GHSA-h82f-cjm4-g22r: Malware in @guicai777/mcp-doctor
- SCA from the title:
GHSA-6r85-j4v5-27rf: Malware in mock-data-sdk
mock-data-sdk >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6r85-j4v5-27rf: Malware
- SCA from the title:
GHSA-8j58-xfpr-cqfv: Malware in motionframe-plugins
motionframe-plugins >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8j58-xfpr-cqfv: Malware
- SCA from the title:
GHSA-v2fg-x378-42g4: Malware in @motionlib/framer-motion
@motionlib/framer-motion >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v2fg-x378-42g4: Malware
- SCA from the title:
GHSA-gmwr-j73c-6xw3: Malware in mayx-blog
mayx-blog = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-gmwr-j73c-6xw3: Malware
- SCA from the title:
GHSA-vwr8-p7j8-qqxg: Malicious code in @fedfub/string-utils (npm)
@fedfub/string-utils = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-vwr8-p7j8-qqxg: Maliciou
- SCA from the title:
GHSA-q6xv-rqvq-8h46: Malicious code in vcdxg-eavtg-util (npm)
vcdxg-eavtg-util = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-q6xv-rqvq-8h46: Maliciou
- SCA from the title:
GHSA-642c-p559-rmr5: Malicious code in truffle-kit (npm)
truffle-kit = 3.3.2 → remove it
Why tagged?
- SCA from the title:
GHSA-642c-p559-rmr5: Maliciou
- SCA from the title:
GHSA-f76h-3xwf-v78w: Malicious code in @ikyerza/baileys (npm)
@ikyerza/baileys = 1.0.0 → remove it | = 1.1.1 → remove it | = 1.2.0 → remove it
Why tagged?
- SCA from the title:
GHSA-f76h-3xwf-v78w: Maliciou
- SCA from the title:
GHSA-4rf3-5pmj-pw8m: Malicious code in @ikyzanx/baileys (npm)
@ikyzanx/baileys = 8.5.6 → remove it
Why tagged?
- SCA from the title:
GHSA-4rf3-5pmj-pw8m: Maliciou
- SCA from the title:
GHSA-h5f6-w383-w67g: Malicious code in @izi-coder/baileys (npm)
@izi-coder/baileys = 2.0.5 → remove it | = 6.0.9 → remove it | = 6.0.10 → remove it
Why tagged?
- SCA from the title:
GHSA-h5f6-w383-w67g: Maliciou
- SCA from the title:
GHSA-m77j-jgx5-q3j7: Malicious code in @fedfub/utils (npm)
@fedfub/utils = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-m77j-jgx5-q3j7: Maliciou
- SCA from the title:
GHSA-7ppq-5qfr-6796: Malicious code in vite-plugin-bar-plus (npm)
vite-plugin-bar-plus = 1.0.47 → remove it
Why tagged?
- SCA from the title:
GHSA-7ppq-5qfr-6796: Maliciou
- SCA from the title:
GHSA-mq6r-xww7-j53j: Malicious code in @iky-erza/baileys (npm)
@iky-erza/baileys = 0.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-mq6r-xww7-j53j: Maliciou
- SCA from the title:
GHSA-jrfq-g54q-gmc8: Malicious code in scanstudy-pointer-bat (npm)
scanstudy-pointer-bat = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-jrfq-g54q-gmc8: Maliciou
- SCA from the title:
GHSA-j9r4-5g27-w8rx: Malicious code in @kingorwot/my-baileys (npm)
@kingorwot/my-baileys = 2.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-j9r4-5g27-w8rx: Maliciou
- SCA from the title:
GHSA-vxx3-mjmc-wgj8: Malicious code in @guicai777/mcp-doctor (npm)
@guicai777/mcp-doctor = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-vxx3-mjmc-wgj8: Maliciou
- AI Security from the title:
GHSA-vxx3-mjmc-wgj8: Malicious code in @guicai777/mcp-doctor (npm)
- SCA from the title:
GHSA-qhrc-mfjw-xwq3: Malicious code in @eryxenx/fca (npm)
@eryxenx/fca = 1.3.2 → remove it | = 1.3.1 → remove it | = 1.3.0 → remove it
Why tagged?
- SCA from the title:
GHSA-qhrc-mfjw-xwq3: Maliciou
- SCA from the title:
GHSA-m6vr-gmw5-vfv7: Malicious code in retry-utils-testmetest (npm)
retry-utils-testmetest = 1.0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-m6vr-gmw5-vfv7: Maliciou
- SCA from the title:
GHSA-cq9c-m7g7-f925: Malicious code in promise-retry-utils-testmetest (npm)
promise-retry-utils-testmetest = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-cq9c-m7g7-f925: Maliciou
- SCA from the title:
GHSA-r4j6-q34r-gc6j: Malicious code in stream-buffer-utils-testmetest (npm)
stream-buffer-utils-testmetest = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-r4j6-q34r-gc6j: Maliciou
- SCA from the title:
GHSA-33v7-c769-3ww7: Malicious code in @awazevr/mfe-common.contexts.guest-auth (npm)
@awazevr/mfe-common.contexts.guest-auth = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-33v7-c769-3ww7: Maliciou
- SCA from the title:
GHSA-w7vf-pf93-jgpv: Malicious code in spencer-braincore (npm)
spencer-braincore = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-w7vf-pf93-jgpv: Maliciou
- SCA from the title:
GHSA-8rw9-x9m5-7353: Malware in @zaiinlin/bails
@zaiinlin/bails >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8rw9-x9m5-7353: Malware
- SCA from the title:
GHSA-phch-78ch-wpcc: Malware in smfos-bskdz-util
smfos-bskdz-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-phch-78ch-wpcc: Malware
- SCA from the title:
GHSA-h68g-7c77-4w37: Malware in nuadg-jhtvh-util
nuadg-jhtvh-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h68g-7c77-4w37: Malware
- SCA from the title:
GHSA-6wmj-hgpg-2pp6: Malware in vcnwi-ihpgp-util
vcnwi-ihpgp-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6wmj-hgpg-2pp6: Malware
- SCA from the title:
GHSA-hq35-gwxr-qq5x: Malware in tsbwt-hawsi-util
tsbwt-hawsi-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hq35-gwxr-qq5x: Malware
- SCA from the title:
GHSA-vm96-5m7m-hr25: Malware in jmrwd-gjdob-util
jmrwd-gjdob-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vm96-5m7m-hr25: Malware
- SCA from the title:
GHSA-6gpf-476p-c87j: Malware in fcefi-wdojs-util
fcefi-wdojs-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6gpf-476p-c87j: Malware
- SCA from the title:
GHSA-6p2g-3r68-5j5w: Malware in glbkm-vrnpk-util
glbkm-vrnpk-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6p2g-3r68-5j5w: Malware
- SCA from the title:
GHSA-6wpr-mmgq-xj72: Malware in csvmw-glair-util
csvmw-glair-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6wpr-mmgq-xj72: Malware
- SCA from the title:
GHSA-r3pq-mfc8-4c4f: Malware in piepa-yfcbf-util
piepa-yfcbf-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-r3pq-mfc8-4c4f: Malware
- SCA from the title:
GHSA-p65r-r93m-c4mj: Malware in oubkt-krxpo-util
oubkt-krxpo-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-p65r-r93m-c4mj: Malware
- SCA from the title:
GHSA-5x2f-rv2j-gxvc: Malware in qtfdd-lnrwx-util
qtfdd-lnrwx-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5x2f-rv2j-gxvc: Malware
- SCA from the title:
GHSA-c2cw-ccqv-pghc: Malware in nhhhh-yhejl-util
nhhhh-yhejl-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c2cw-ccqv-pghc: Malware
- SCA from the title:
GHSA-frxp-365q-8p36: Malware in teahy-znrpz-util
teahy-znrpz-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-frxp-365q-8p36: Malware
- SCA from the title:
GHSA-gcx6-6r3h-7cvr: Malware in vojmd-ajgkr-util
vojmd-ajgkr-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gcx6-6r3h-7cvr: Malware
- SCA from the title:
GHSA-4ffv-gw64-v99f: Malware in xueoj-vjtof-util
xueoj-vjtof-util >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4ffv-gw64-v99f: Malware
- SCA from the title:
GHSA-c5fp-459q-c9pp: Malware in dxrs-dos
dxrs-dos >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c5fp-459q-c9pp: Malware
- SCA from the title:
GHSA-ghgg-v8r8-pfc3: Malicious code in sirens-lamentt (npm)
sirens-lamentt = 99.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-ghgg-v8r8-pfc3: Maliciou
- SCA from the title:
GHSA-822g-7r9h-j5w4: Malicious code in webhook-easy (npm)
webhook-easy = 1.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-822g-7r9h-j5w4: Maliciou
- SCA from the title:
GHSA-fg8p-3m89-pwhf: Malicious code in @cexy/wonfca (npm)
@cexy/wonfca = 1.2.2 → remove it | = 1.2.1 → remove it
Why tagged?
- SCA from the title:
GHSA-fg8p-3m89-pwhf: Maliciou
- SCA from the title:
GHSA-mc8w-wjhw-45x5 / CVE-2026-114516: Etherpad: Pre-auth arbitrary file read
ep_etherpad-lite >= 1.8.14, < 3.3.3 → 3.3.3
Why tagged?
- SCA from the title:
GHSA-mc8w-wjhw-45x5 / CVE-202
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
25 PyPI security advisories
GHSA-53pm-wgxf-c6qf / CVE-2026-132276: wcmatch: Polynomial-time ReDoS when matching untrusted names against multi-star patterns (default flags)
wcmatch <= 11.1 → 11.2
Why tagged?
- SCA from the title:
GHSA-53pm-wgxf-c6qf / CVE-202
- SCA from the title:
GHSA-q87h-c5m7-659j / CVE-2026-132277: Inscriptis: Quadratic memory growth from sibling <table> elements in get_text()
inscriptis >= 2.0.0, <= 2.7.5 → 2.7.6
Why tagged?
- SCA from the title:
GHSA-q87h-c5m7-659j / CVE-202
- SCA from the title:
GHSA-555j-qj3j-c8jv / CVE-2026-132275: svglib: Exponential resource consumption via nested <use> references in svg2rlg
svglib <= 2.3.0 → 2.3.1
Why tagged?
- SCA from the title:
GHSA-555j-qj3j-c8jv / CVE-202
- SCA from the title:
GHSA-72jh-722p-rqr3 / CVE-2026-77331: memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session
memtomem-stm >= 0.1.2, <= 0.1.33 → 0.1.34
Why tagged?
- SCA from the title:
GHSA-72jh-722p-rqr3 / CVE-202
- SCA from the title:
GHSA-43hx-xm7w-3mhj / CVE-2026-77332: memtomem-stm: Surfaced memory data can escape the Markdown compatibility boundary
memtomem-stm >= 0.1.0, <= 0.1.33 → 0.1.34
Why tagged?
- SCA from the title:
GHSA-43hx-xm7w-3mhj / CVE-202
- SCA from the title:
GHSA-jrjx-9jjw-747m / CVE-2026-77309: AIT-GUI route chain allows unauthenticated Python execution in server process
ait-gui >= 1.0.0, <= 2.5.0 → 2.5.1
Why tagged?
- SCA from the title:
GHSA-jrjx-9jjw-747m / CVE-202
- SCA from the title:
GHSA-jq64-f5cw-4m63: Malicious code in wouki-lipok (PyPI)
wouki-lipok = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-jq64-f5cw-4m63: Maliciou
- SCA from the title:
GHSA-4ccc-7rf5-f7fr: Malicious code in delta-nested-filter-tracer (PyPI)
delta-nested-filter-tracer = 1.0.0 → remove it | = 1.0.0.post1 → remove it
Why tagged?
- SCA from the title:
GHSA-4ccc-7rf5-f7fr: Maliciou
- SCA from the title:
GHSA-4qjx-cpx9-x936: Malicious code in pkgreg-buildprobe-16c409218045 (PyPI)
pkgreg-buildprobe-16c409218045 = 0.0.1 → remove it | = 0.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-4qjx-cpx9-x936: Maliciou
- SCA from the title:
GHSA-ggc8-jm8h-f86f: Malicious code in scope-token-fetch-vector (PyPI)
scope-token-fetch-vector = 1.0.0 → remove it | = 1.0.0.post1 → remove it
Why tagged?
- SCA from the title:
GHSA-ggc8-jm8h-f86f: Maliciou
- SCA from the title:
GHSA-hgqv-p73h-wm6f: Malicious code in cijukop (PyPI)
cijukop = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-hgqv-p73h-wm6f: Maliciou
- SCA from the title:
GHSA-8hrc-gqpq-gwpv: Malicious code in testing1345py (PyPI)
testing1345py = 0.1.3 → remove it | = 0.1.4 → remove it
Why tagged?
- SCA from the title:
GHSA-8hrc-gqpq-gwpv: Maliciou
- SCA from the title:
GHSA-6499-jgj4-2wpf / CVE-2026-104773: CKAN: Session Fixation in Registration View
ckan < 2.10.11 → 2.10.11 | >= 2.11.0, < 2.11.6 → 2.11.6
Why tagged?
- SCA from the title:
GHSA-6499-jgj4-2wpf / CVE-202
- SCA from the title:
GHSA-wcqj-wx85-c75p / CVE-2026-130176: aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
amqtt >= 0.11.0, <= 0.12.0 → 0.12.1
Why tagged?
- SCA from the title:
GHSA-wcqj-wx85-c75p / CVE-202
- SCA from the title:
GHSA-2hjf-7455-w946 / CVE-2026-104199: aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
amqtt >= 0.11.0, <= 0.11.3 → 0.11.4
Why tagged?
- SCA from the title:
GHSA-2hjf-7455-w946 / CVE-202
- SCA from the title:
GHSA-5q5c-h8xj-h3fp: Malicious code in mrcl2suhail (PyPI)
MRCL2Suhail = 1.0.1 → remove it | = 1.0.3 → remove it | = 1.0.4 → remove it | = 1.0.2 → remove it | = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-5q5c-h8xj-h3fp: Maliciou
- SCA from the title:
GHSA-f3g9-pmww-pww3: Malicious code in mrcl2 (PyPI)
MRCL2 = 1.0.5 → remove it | = 1.0.2 → remove it | = 1.0.1 → remove it | = 1.0.3 → remove it | = 1.0.4 → remove it
Why tagged?
- SCA from the title:
GHSA-f3g9-pmww-pww3: Maliciou
- SCA from the title:
GHSA-v97v-7r82-xcjg: Malicious code in certify-web (PyPI)
certify-web = 0.1.3 → remove it
Why tagged?
- SCA from the title:
GHSA-v97v-7r82-xcjg: Maliciou
- SCA from the title:
GHSA-9x8x-crjq-g64h / CVE-2026-77359: Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes
jupyter-mcp-server <= 1.0.2 → 1.0.3
Why tagged?
- SCA from the title:
GHSA-9x8x-crjq-g64h / CVE-202
- SCA from the title:
GHSA-24pw-rf5p-mgp7 / CVE-2026-77318: Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode
jupyter-mcp-server <= 1.0.2 → 1.0.3
Why tagged?
- SCA from the title:
GHSA-24pw-rf5p-mgp7 / CVE-202
- SCA from the title:
GHSA-6pm8-6f34-9v3g / CVE-2026-77316: Flyto2 Core: SSRF guard bypass via DNS rebinding (validate_url_ssrf resolves-then-connects without pinning)
flyto-core <= 2.26.7 → 2.26.8
Why tagged?
- SCA from the title:
GHSA-6pm8-6f34-9v3g / CVE-202
- SCA from the title:
GHSA-2mr3-rxrq-238c / CVE-2026-77315: Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation
flyto-core <= 2.26.7 → 2.26.8
Why tagged?
- SCA from the title:
GHSA-2mr3-rxrq-238c / CVE-202
- SCA from the title:
GHSA-pfg2-w999-497v / CVE-2026-77313: Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU
flyto-core <= 2.26.7 → 2.26.8
Why tagged?
- SCA from the title:
GHSA-pfg2-w999-497v / CVE-202
- SCA from the title:
GHSA-p34x-fmph-9fjx / CVE-2026-77312: Flyto2 Core: Arbitrary file write via unguarded data.*/file.* modules (incomplete fix of CVE-2026-67429)
flyto-core <= 2.26.7 → 2.26.8
Why tagged?
- SCA from the title:
GHSA-p34x-fmph-9fjx / CVE-202
- SCA from the title:
GHSA-86mf-q4h5-69gp / CVE-2026-59988: django-docutils unsafe Docutils defaults allow local file disclosure, SSRF, and stored XSS
django-docutils < 0.30.0 → 0.30.0
Why tagged?
- SCA from the title:
GHSA-86mf-q4h5-69gp / CVE-202
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
15 Packagist security advisories
GHSA-h57j-5f5m-789v / CVE-2026-104884: contao/core-bundle: Cross-site scripting in the frontend search results
contao/core-bundle >= 4.9.0, < 5.3.50 → 5.3.50 | >= 5.4.0-RC1, < 5.7.12 → 5.7.12
Why tagged?
- SCA from the title:
GHSA-h57j-5f5m-789v / CVE-202
- SCA from the title:
GHSA-r9qp-pqx5-8369 / CVE-2026-104883: contao/core-bundle: Non-admin users can self-grant permissions that implicitly make them administrators
contao/core-bundle >= 5.0.0, < 5.3.50 → 5.3.50 | >= 5.4.0-RC1, < 5.7.12 → 5.7.12
Why tagged?
- SCA from the title:
GHSA-r9qp-pqx5-8369 / CVE-202
- SCA from the title:
GHSA-23w9-4pg3-xwm3 / CVE-2026-104882: contao/core-bundle: Improper access control in the CSV import wizard
contao/core-bundle >= 5.0.0, < 5.3.50 → 5.3.50 | >= 5.4.0-RC1, < 5.7.12 → 5.7.12
Why tagged?
- SCA from the title:
GHSA-23w9-4pg3-xwm3 / CVE-202
- SCA from the title:
GHSA-3r9g-pfhv-3228 / CVE-2026-104881: contao/newsletter-bundle: Contao newsletter custom actions bypass channel-scoped authorization
contao/newsletter-bundle >= 5.0.0, < 5.3.50 → 5.3.50 | >= 5.4.0-RC1, < 5.7.12 → 5.7.12
Why tagged?
- SCA from the title:
GHSA-3r9g-pfhv-3228 / CVE-202
- SCA from the title:
GHSA-prhx-9q2h-ph2x / CVE-2026-103026: Paymenter: Unauthenticated arbitrary method invocation in Livewire components
paymenter/paymenter <= 1.5.6 → 1.5.7
Why tagged?
- SCA from the title:
GHSA-prhx-9q2h-ph2x / CVE-202
- SCA from the title:
GHSA-9657-8vc2-7g2p / CVE-2026-115463: Poweradmin: The email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout, so an attacker holding the password can brute-force it within the validity window
poweradmin/poweradmin >= 4.0.0, < 4.2.6 → 4.2.6 | >= 4.3.0, < 4.3.5 → 4.3.5 | >= 4.4.0, < 4.4.1 → 4.4.1
Why tagged?
- SCA from the title:
GHSA-9657-8vc2-7g2p / CVE-202
- SCA from the title:
GHSA-66q9-mxf2-xqw6 / CVE-2026-103035: TeamPass folder re-parenting authorization bypass
nilsteampassnet/TeamPass < 3.2.2.0 → 3.2.2.0
Why tagged?
- SCA from the title:
GHSA-66q9-mxf2-xqw6 / CVE-202
- SCA from the title:
GHSA-wgvx-x5g3-9v29 / CVE-2026-63012: baserCMS administrative API authorization bypass through session fallback
baserproject/baser-core <= 5.2.3 → 5.3.0
Why tagged?
- SCA from the title:
GHSA-wgvx-x5g3-9v29 / CVE-202
- SCA from the title:
GHSA-2pj4-v76f-wjvx / CVE-2026-62955: baserCMS: Path Traversal Bypass via realpath() in BcThemeFileService (CVE-2026-30940 Patch Bypass)
baserproject/baser-core < 5.3.0 → 5.3.0
Why tagged?
- SCA from the title:
GHSA-2pj4-v76f-wjvx / CVE-202
- Remediation from the title:
Service (CVE-2026-30940 Patch Bypass)
- SCA from the title:
GHSA-r7h9-qx4h-77j5 / CVE-2026-77378: Bolt ListFormatHelper SQL injection
bolt/core < 6.1.4 → 6.1.4
Why tagged?
- SCA from the title:
GHSA-r7h9-qx4h-77j5 / CVE-202
- SCA from the title:
GHSA-3xjf-9q55-vxw4 / CVE-2026-77380: Bolt: Prevent SSRF due to unchecked followed redirects
bolt/core < 6.1.5 → 6.1.5
Why tagged?
- SCA from the title:
GHSA-3xjf-9q55-vxw4 / CVE-202
- SCA from the title:
GHSA-6358-jg5p-hmjj / CVE-2026-77379: Bolt: Information disclosure through unfiltered public relation API endpoint
bolt/core < 6.1.4 → 6.1.4
Why tagged?
- SCA from the title:
GHSA-6358-jg5p-hmjj / CVE-202
- SCA from the title:
GHSA-2535-j2pq-qq4r / CVE-2026-77377: Bolt: Server-Side Request Forgery (SSRF) in URL-upload and embed endpoints
bolt/core < 6.1.4 → 6.1.4
Why tagged?
- SCA from the title:
GHSA-2535-j2pq-qq4r / CVE-202
- SCA from the title:
GHSA-xr6g-7g83-j865 / CVE-2026-77376: Bolt: Open redirect enables post-authentication redirection to arbitrary domains
bolt/core < 6.1.4 → 6.1.4
Why tagged?
- SCA from the title:
GHSA-xr6g-7g83-j865 / CVE-202
- SCA from the title:
GHSA-c3cj-3p6p-j822 / CVE-2026-63415: Jane: $ref resolution performs SSRF + LFI (path traversal) at code-generation time (jane-php)
jane-php/open-api-3 < 7.12.0 → 7.12.0
Why tagged?
- SCA from the title:
GHSA-c3cj-3p6p-j822 / CVE-202
- SCA from the title:
All Packagist advisories · each advisory is independent, not one campaign
6 crates.io security advisories
GHSA-qh76-45cr-8xrc / CVE-2026-61725: sevenz-rust2: decompress builds each output path as dest.join(entry.name()) with no traversal guard, allowing a crafted .7z to write files outside the destination (Zip-Slip)
sevenz-rust2 < 0.21.1 → 0.21.1
Why tagged?
- SCA from the title:
GHSA-qh76-45cr-8xrc / CVE-202
- SCA from the title:
GHSA-9rv8-9hvg-92mq / CVE-2026-35376: chcon: recursive relabel not anchored to traversal dirfd (TOCTOU)
uu_chcon <= 0.9.0 → 0.10.0
Why tagged?
- SCA from the title:
GHSA-9rv8-9hvg-92mq / CVE-202
- SCA from the title:
GHSA-xhrc-7f76-vh96 / CVE-2026-35377: uu_env incorrectly rejects backslashes within single-quoted strings accepted by GNU env
uu_env <= 0.9.0 → 0.10.0
Why tagged?
- SCA from the title:
GHSA-xhrc-7f76-vh96 / CVE-202
- SCA from the title:
GHSA-fjjq-8hw5-cf9f / CVE-2026-35374: split: TOCTOU output-open allows truncating a swapped file
uu_split <= 0.9.0 → 0.10.0
Why tagged?
- SCA from the title:
GHSA-fjjq-8hw5-cf9f / CVE-202
- SCA from the title:
GHSA-25rm-9wvm-m38v / CVE-2026-77382: falcon-rust: Discrete-Gaussian sampler runs at 2^-33 precision, far below Falcon's requirement (reference KAT vectors no longer pass)
falcon-rust <= 0.1.3 → 0.2.0
Why tagged?
- SCA from the title:
GHSA-25rm-9wvm-m38v / CVE-202
- SCA from the title:
GHSA-x26x-7f4v-cqx7 / CVE-2026-62337: snark-verifier: Halo 2 aggregation circuit mishandles point-at-infinity proof elements
snark-verifier < 0.2.5 → 0.2.6
Why tagged?
- SCA from the title:
GHSA-x26x-7f4v-cqx7 / CVE-202
- SCA from the title:
All crates.io advisories · each advisory is independent, not one campaign
16 Go security advisories
GHSA-p3j5-5hrq-p75h / CVE-2026-58254: nats-server Leaf node connections bypass Nats-Trace-Dest permission check
github.com/nats-io/nats-server/v2 < 2.12.8 → 2.12.8 | >= 2.14.0-RC.1, < 2.14.3 → 2.14.3
Why tagged?
- SCA from the title:
GHSA-p3j5-5hrq-p75h / CVE-202
- SCA from the title:
GHSA-x72p-hmqp-46hw / CVE-2026-105803: Git LFS may execute arbitrary commands via crafted Git LFS configurations
github.com/git-lfs/git-lfs >= 1.3.0, <= 2.13.3 → no fix; github.com/git-lfs/git-lfs/v3 >= 3.0.0, < 3.8.1 → 3.8.1 · partly fixed
Why tagged?
- SCA from the title:
GHSA-x72p-hmqp-46hw / CVE-202
- SCA from the title:
GHSA-xrgv-7vx6-5vx6 / CVE-2026-105802: Git LFS may execute arbitrary commands via crafted Git configurations
github.com/git-lfs/git-lfs >= 0.6.0, <= 2.13.3 → no fix; github.com/git-lfs/git-lfs/v3 >= 3.0.0, < 3.8.1 → 3.8.1 · partly fixed
Why tagged?
- SCA from the title:
GHSA-xrgv-7vx6-5vx6 / CVE-202
- SCA from the title:
GHSA-4hrh-34w3-5ww8 / CVE-2026-104099: Fabio: Access-control bypass through unnormalized request paths
github.com/fabiolb/fabio < 1.7.3 → 1.7.3
Why tagged?
- SCA from the title:
GHSA-4hrh-34w3-5ww8 / CVE-202
- SCA from the title:
GHSA-x7xj-4j4f-88xr / CVE-2026-69261: Git LFS may leak HTTP headers after redirections
github.com/git-lfs/git-lfs >= 0.5.0, <= 2.13.3 → no fix; github.com/git-lfs/git-lfs/v3 >= 3.0.0, < 3.8.1 → 3.8.1 · partly fixed
Why tagged?
- SCA from the title:
GHSA-x7xj-4j4f-88xr / CVE-202
- SCA from the title:
GHSA-w3f2-pr6x-wwjc / CVE-2026-69260: Git LFS may attempt arbitrary remote commands via crafted SSH URLs
github.com/git-lfs/git-lfs >= 0.5.0, <= 2.13.3 → no fix; github.com/git-lfs/git-lfs/v3 >= 3.0.0, < 3.8.1 → 3.8.1 · partly fixed
Why tagged?
- SCA from the title:
GHSA-w3f2-pr6x-wwjc / CVE-202
- SCA from the title:
GHSA-hghq-53p7-c582 / CVE-2026-115578: go-guerrilla crashes on a bare XCLIENT command (7-byte slice off-by-one panic)
github.com/phires/go-guerrilla = 1.6.7 → no fix | < 1.6.7-1 → 1.6.7-1 · partly fixed
Why tagged?
- SCA from the title:
GHSA-hghq-53p7-c582 / CVE-202
- SCA from the title:
GHSA-v9v2-98xq-627c / CVE-2026-104129: pREST _groupby function-expression SQL injection (incomplete fix of CVE-2025-58450)
github.com/prest/prest <= 1.5.5 → no fix; github.com/prest/prest/v2 <= 2.3.0 → 2.4.0 · partly fixed
Why tagged?
- SCA from the title:
GHSA-v9v2-98xq-627c / CVE-202
- SCA from the title:
GHSA-gfwj-45pc-w6r5 / CVE-2026-103033: ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData
github.com/altcha-org/altcha-lib-go/v2 >= 2.0.0, < 2.1.0 → 2.1.0
Why tagged?
- SCA from the title:
GHSA-gfwj-45pc-w6r5 / CVE-202
- SCA from the title:
GHSA-7hvw-3c2q-45qg / CVE-2026-103025: bep/imagemeta: Unbounded memory allocation decoding PNG `zTXt` "Raw profile type iptc" chunks
github.com/bep/imagemeta < 0.17.3 → 0.17.3
Why tagged?
- SCA from the title:
GHSA-7hvw-3c2q-45qg / CVE-202
- SCA from the title:
GHSA-v6w5-38cf-pcv8 / CVE-2026-102945: Aether Project amf: panic on an unrecovered NGAP goroutine
github.com/omec-project/amf < 1.7.1-0.20260725031321-d28042aaaea0 → 1.7.1-0.20260725031321-d28042aaaea0
Why tagged?
- SCA from the title:
GHSA-v6w5-38cf-pcv8 / CVE-202
- SCA from the title:
GHSA-wj7x-58c2-5793 / CVE-2026-77369: Daptin: Broken Access Control (IDOR) in the generic YJS collaboration endpoint
github.com/daptin/daptin >= 0.11.4, < 0.12.30 → 0.12.30
Why tagged?
- SCA from the title:
GHSA-wj7x-58c2-5793 / CVE-202
- SCA from the title:
GHSA-hq2p-f2vj-v3cm / CVE-2026-77367: Daptin: Unauthenticated SQL Injection via the `sort` query parameter on every entity list endpoint
github.com/daptin/daptin <= 0.12.29 → 0.12.30
Why tagged?
- SCA from the title:
GHSA-hq2p-f2vj-v3cm / CVE-202
- SCA from the title:
GHSA-p957-7v2w-g93g / CVE-2026-58208: NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled
github.com/nats-io/nats-server/v2 < 2.12.12 → 2.12.12 | >= 2.14.0-RC.1, < 2.14.3 → 2.14.3
Why tagged?
- SCA from the title:
GHSA-p957-7v2w-g93g / CVE-202
- SCA from the title:
GHSA-r72h-j7qq-v6qg / CVE-2026-58210: NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets
github.com/nats-io/nats-server/v2 < 2.12.12 → 2.12.12 | >= 2.14.0-RC.1, < 2.14.3 → 2.14.3
Why tagged?
- SCA from the title:
GHSA-r72h-j7qq-v6qg / CVE-202
- SCA from the title:
GHSA-7qmq-8cc4-hxwg / CVE-2026-58209: NATS Server MQTT retained messages and QoS replay bypass subscription deny rules
github.com/nats-io/nats-server/v2 < 2.12.12 → 2.12.12 | >= 2.14.0-RC.1, < 2.14.3 → 2.14.3
Why tagged?
- SCA from the title:
GHSA-7qmq-8cc4-hxwg / CVE-202
- SCA from the title:
All Go advisories · each advisory is independent, not one campaign
2 Maven security advisories
GHSA-cg26-4c6j-2x8h / CVE-2026-69133: netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges
io.netty.incubator:netty-incubator-codec-ohttp >= 0.0.20.Final, <= 0.0.26.Final → 0.0.27.Final
Why tagged?
- SCA from the title:
GHSA-cg26-4c6j-2x8h / CVE-202
- SCA from the title:
GHSA-3h6w-xcw3-9xjj / CVE-2026-104885: OpenRemote: Cross-realm MQTT session disconnect without authorization
io.openremote:openremote-manager < 1.31.0 → 1.31.0
Why tagged?
- SCA from the title:
GHSA-3h6w-xcw3-9xjj / CVE-202
- SCA from the title:
All Maven advisories · each advisory is independent, not one campaign
4 NuGet security advisories
GHSA-x6w4-f264-3vvr / CVE-2026-63184: Refitter: Unrestricted OpenAPI references permit build-host SSRF and file inclusion
Refitter < 2.1.1 → 2.1.1
Why tagged?
- SCA from the title:
GHSA-x6w4-f264-3vvr / CVE-202
- SCA from the title:
GHSA-p32v-8v8j-j534 / CVE-2026-63344: Refitter allows arbitrary code execution through unescaped OpenAPI content-type values
Refitter < 2.1.2 → 2.1.2
Why tagged?
- SCA from the title:
GHSA-p32v-8v8j-j534 / CVE-202
- SCA from the title:
GHSA-58x9-vjvp-6mx8 / CVE-2026-63346: Refitter allows code execution through unescaped OpenAPI header parameter names
Refitter < 2.1.2 → 2.1.2
Why tagged?
- SCA from the title:
GHSA-58x9-vjvp-6mx8 / CVE-202
- SCA from the title:
GHSA-3fhm-p725-h3g3 / CVE-2026-63345: Refitter allows arbitrary code execution through unescaped OpenAPI paths
Refitter < 2.1.2 → 2.1.2
Why tagged?
- SCA from the title:
GHSA-3fhm-p725-h3g3 / CVE-202
- SCA from the title:
All NuGet advisories · each advisory is independent, not one campaign
27 PyPI security advisories
GHSA-wr3g-j6qj-xpgh / CVE-2026-128135: NLTK: ZIP package extraction follows in-root hardlinks and overwrites files outside the NLTK data root
nltk >= 3.9.4, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-wr3g-j6qj-xpgh / CVE-202
- SCA from the title:
GHSA-c59x-vh6j-3w8v / CVE-2026-128136: NLTK: AllowlistUnpickler does not deny numpy submodule-local file-I/O sinks
nltk >= 3.10.0, < 3.10.4 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-c59x-vh6j-3w8v / CVE-202
- SCA from the title:
GHSA-g58v-j9g9-5gfg / CVE-2026-128137: NLTK corpus-reader view methods bypass the scoped root sandbox via intermediate-directory symlinks
nltk >= 3.9.4, < 3.10.4 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-g58v-j9g9-5gfg / CVE-202
- SCA from the title:
GHSA-x8q7-6c7m-52gw / CVE-2026-128138: NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments
nltk >= 3.10.3, < 3.10.4 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-x8q7-6c7m-52gw / CVE-202
- SCA from the title:
GHSA-j8g8-j4j7-8j54 / CVE-2026-128139: NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
nltk >= 3.6, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-j8g8-j4j7-8j54 / CVE-202
- SCA from the title:
GHSA-pcm8-fqjx-rvx8 / CVE-2026-128140: NLTK: Downloader cyclic collection indices cause an infinite closure walk
nltk >= 3.6.7, < 3.10.4 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-pcm8-fqjx-rvx8 / CVE-202
- SCA from the title:
GHSA-9ffx-rrgx-mhgx / CVE-2026-129221: NLTK: ARFF_Formatter Injects Weka ARFF Schema Directives via Attacker-Controlled Class Labels
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-9ffx-rrgx-mhgx / CVE-202
- SCA from the title:
GHSA-rh8m-wqhc-qmrf / CVE-2026-129222: Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in DependencyGraph.tree()/triples()
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-rh8m-wqhc-qmrf / CVE-202
- SCA from the title:
GHSA-8846-p9w9-5frf / CVE-2026-129223: Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in Synset.tree()/acyclic_tree() via WordNet relation traversal
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-8846-p9w9-5frf / CVE-202
- SCA from the title:
GHSA-3h95-x772-4765 / CVE-2026-129224: NLTK: Uncontrolled recursion in CCG lexicon parser causes denial of service via deeply nested category input
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-3h95-x772-4765 / CVE-202
- SCA from the title:
GHSA-xfcv-m889-fmqg / CVE-2026-129225: NLTK: Uncontrolled recursion in DependencyGraph traversal causes denial of service via deep dependency chains
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-xfcv-m889-fmqg / CVE-202
- SCA from the title:
GHSA-gm9r-hvc9-96gv / CVE-2026-129304: Guard Core: Unvalidated X-Forwarded-For-derived string used as a Redis key component and interpolated into a KEYS glob pattern
guard-core >= 1.0.0, < 3.13.0 → 3.13.0
Why tagged?
- SCA from the title:
GHSA-gm9r-hvc9-96gv / CVE-202
- SCA from the title:
GHSA-w7wg-6q7v-44f2 / CVE-2026-129303: Guard Core: Whitespace-collapse preprocessing permanently disables the CRLF-anchored http-splitting and command-injection detectors in the default detection mode
guard-core >= 1.0.0, < 3.13.0 → 3.13.0
Why tagged?
- SCA from the title:
GHSA-w7wg-6q7v-44f2 / CVE-202
- SCA from the title:
GHSA-r7hm-rjvg-xx7j / CVE-2026-129302: Guard Core: Quadratic ReDoS in built-in detection pattern freezes the event loop with a single request
guard-core >= 3.5.0, <= 3.12.0 → 3.13.0
Why tagged?
- SCA from the title:
GHSA-r7hm-rjvg-xx7j / CVE-202
- SCA from the title:
GHSA-m4g8-47f9-h588 / CVE-2026-129307: eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing
eml-parser <= 3.0.3 → 3.0.4
Why tagged?
- SCA from the title:
GHSA-m4g8-47f9-h588 / CVE-202
- SCA from the title:
GHSA-qx49-fqc8-xw99 / CVE-2026-115563: Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
mcp >= 2.0.0a1, < 2.2.0 → 2.2.0 | >= 1.9.1, < 1.30.0 → 1.30.0
Why tagged?
- SCA from the title:
GHSA-qx49-fqc8-xw99 / CVE-202
- AI Security from the title:
OAuth client could send credentials to an authorization server chosen by the MCP server
- SCA from the title:
GHSA-phmp-hrw4-r36r / CVE-2026-97698: Mistune: Quadratic-time DoS in parse_link_href via unbounded parenthesis scan on empty-label links
mistune < 3.3.4 → 3.3.4
Why tagged?
- SCA from the title:
GHSA-phmp-hrw4-r36r / CVE-202
- SCA from the title:
GHSA-ww7q-mxrj-5ffg / CVE-2026-97699: Mistune: Quadratic-time DoS in inline image parsing (precedence_scan) bypasses not-is-image guards
mistune < 3.3.4 → 3.3.4
Why tagged?
- SCA from the title:
GHSA-ww7q-mxrj-5ffg / CVE-202
- SCA from the title:
GHSA-56v3-jrq2-4q9m / CVE-2026-77597: iSponsorBlockTV: SSRF via Malicious SSDP Response Spoofing in Local Device Discovery
iSponsorBlockTV <= 2.10.0 → 2.11.0
Why tagged?
- SCA from the title:
GHSA-56v3-jrq2-4q9m / CVE-202
- SCA from the title:
GHSA-r7wg-f7r2-8wf7 / CVE-2026-76818: Axon: Download of Code Without Integrity Check in axon-mcp
axon-mcp <= 0.1.0 → no fix
Why tagged?
- SCA from the title:
GHSA-r7wg-f7r2-8wf7 / CVE-202
- SCA from the title:
GHSA-pj7p-238h-76pv / CVE-2026-69139: djangocms-moderation: Moderation comments disclosed to non-participant staff via the admin changelist
djangocms-moderation <= 2.3.0 → 2.4.0
Why tagged?
- SCA from the title:
GHSA-pj7p-238h-76pv / CVE-202
- SCA from the title:
GHSA-8776-qf3h-26r3 / CVE-2026-71535: Mareforma: Unsigned Claims Can Be Promoted to REPLICATED via Missing Signature Enforcement in Convergence Path
mareforma >= 0.3.0, < 0.3.7 → 0.3.7
Why tagged?
- SCA from the title:
GHSA-8776-qf3h-26r3 / CVE-202
- SCA from the title:
GHSA-xfq4-8hf9-5h43 / CVE-2026-71534: Mareforma: transparency_logged trusts the unsigned rekor block
mareforma >= 0.3.0, < 0.3.8 → 0.3.8
Why tagged?
- SCA from the title:
GHSA-xfq4-8hf9-5h43 / CVE-202
- SCA from the title:
GHSA-rgg9-956j-3378 / CVE-2026-71500: Mareforma: invalidated claims still promote to REPLICATED
mareforma >= 0.3.0, < 0.3.8 → 0.3.8
Why tagged?
- SCA from the title:
GHSA-rgg9-956j-3378 / CVE-202
- SCA from the title:
GHSA-hxh5-gp44-rc6p / CVE-2026-71536: Mareforma: verify_bundle never checks a per-claim signature
mareforma >= 0.3.0, < 0.3.8 → 0.3.8
Why tagged?
- SCA from the title:
GHSA-hxh5-gp44-rc6p / CVE-202
- SCA from the title:
GHSA-m29v-3g7g-9c63 / CVE-2026-71533: Mareforma: search_claims skips verify-on-read, serving forged rows
mareforma = 0.3.7 → 0.3.8
Why tagged?
- SCA from the title:
GHSA-m29v-3g7g-9c63 / CVE-202
- SCA from the title:
GHSA-q9fg-wfvh-ggp3: Malicious code in flo-pro-adk (PyPI)
flo-pro-adk = 0.0.0 → remove it | = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-q9fg-wfvh-ggp3: Maliciou
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
150 npm security advisories
GHSA-wq4f-hq55-wf9w: Malware in ct-fivem
ct-fivem >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wq4f-hq55-wf9w: Malware
- SCA from the title:
GHSA-g682-2jxm-42xh: Malware in aciaiaggu-idat-gfda
aciaiaggu-idat-gfda = 1.1.2 → remove it
Why tagged?
- SCA from the title:
GHSA-g682-2jxm-42xh: Malware
- SCA from the title:
GHSA-p98v-v2hr-rrxr: Malware in abyil-nionai-lasuk
abyil-nionai-lasuk = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-p98v-v2hr-rrxr: Malware
- SCA from the title:
GHSA-6692-fm7p-jj3q: Malware in abyil-nina-lasuk
abyil-nina-lasuk = 1.3.3 → remove it
Why tagged?
- SCA from the title:
GHSA-6692-fm7p-jj3q: Malware
- SCA from the title:
GHSA-f488-9hp8-qv8h: Malware in abyikula-nioybnali-lauykia
abyikula-nioybnali-lauykia = 1.1.3 → remove it
Why tagged?
- SCA from the title:
GHSA-f488-9hp8-qv8h: Malware
- SCA from the title:
GHSA-v56h-584w-6f7p: Malware in abukhalid
abukhalid = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-v56h-584w-6f7p: Malware
- SCA from the title:
GHSA-4gr2-c235-xq3h: Malware in abina-amugmi-amm
abina-amugmi-amm = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-4gr2-c235-xq3h: Malware
- SCA from the title:
GHSA-7h99-fgqf-hr3c: Malware in abiba-avin-aumauna
abiba-avin-aumauna = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-7h99-fgqf-hr3c: Malware
- SCA from the title:
GHSA-hj9c-qx2w-g7mh / CVE-2026-107853: tiny-secp256k1: Stale buffer after ignored wasm failure accepts invalid infinity tweak
tiny-secp256k1 >= 2.1.0, < 2.2.5 → 2.2.5; @bitcoin-js/tiny-secp256k1-asmjs >= 2.2.2, < 2.2.5 → 2.2.5
Why tagged?
- SCA from the title:
GHSA-hj9c-qx2w-g7mh / CVE-202
- SCA from the title:
GHSA-4rj4-rcrq-gr92: Safari MCP: JavaScript injection through single-quoted tool arguments (backslash not escaped)
safari-mcp < 2.22.15 → 2.22.15
Why tagged?
- SCA from the title:
GHSA-4rj4-rcrq-gr92: Safari M
- AI Security from the title:
-4rj4-rcrq-gr92: Safari MCP: JavaScript injection through single-quote
- SCA from the title:
GHSA-7589-6fvf-x4pw / CVE-2026-121707: Effect: ReDoS in Schema.TemplateLiteral compiled regex
effect <= 3.22.0 → 3.22.1
Why tagged?
- SCA from the title:
GHSA-7589-6fvf-x4pw / CVE-202
- SCA from the title:
GHSA-mx6p-3fg7-v6pj / CVE-2026-77283: obsidian-sync-mcp: Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS rebinding (no-auth mode)
obsidian-sync-mcp <= 0.5.6 → 0.5.7
Why tagged?
- SCA from the title:
GHSA-mx6p-3fg7-v6pj / CVE-202
- SCA from the title:
GHSA-833v-v58w-294h / CVE-2026-76807: Todoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server
@doist/todoist-mcp <= 10.3.2 → 10.3.3
Why tagged?
- SCA from the title:
GHSA-833v-v58w-294h / CVE-202
- SCA from the title:
GHSA-4c2f-96cf-f5fc / CVE-2026-75522: OpenID4VP: X.509 chain validation accepts a forged certificate that reuses a trusted anchor's Subject DN without verifying its signature
@openeudi/openid4vp <= 0.8.0 → 0.8.1
Why tagged?
- SCA from the title:
GHSA-4c2f-96cf-f5fc / CVE-202
- SCA from the title:
GHSA-7qwg-r443-84p9: Malware in vp-baileys
vp-baileys = 0.0.0-stage → remove it | = 9.0.34 → remove it
Why tagged?
- SCA from the title:
GHSA-7qwg-r443-84p9: Malware
- SCA from the title:
GHSA-f8vg-jp77-mvx4: Malware in @andrewstory18/is-real-odd
@andrewstory18/is-real-odd >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f8vg-jp77-mvx4: Malware
- SCA from the title:
GHSA-pm45-rm93-2g47: Malware in item-validates
item-validates >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pm45-rm93-2g47: Malware
- SCA from the title:
GHSA-2r45-7hg7-w99r: Malware in @mibbp/agent-observer
@mibbp/agent-observer >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2r45-7hg7-w99r: Malware
- SCA from the title:
GHSA-mf5v-3qmw-mv6q: Malware in @poucode/baileys
@poucode/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mf5v-3qmw-mv6q: Malware
- SCA from the title:
GHSA-v228-pf8g-jx8g: Malware in npmresearch2026-scope-test
npmresearch2026-scope-test >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v228-pf8g-jx8g: Malware
- SCA from the title:
GHSA-5jcj-xh7v-92qr: Malware in scope-test-af5c5e
scope-test-af5c5e >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5jcj-xh7v-92qr: Malware
- SCA from the title:
GHSA-rj9g-592x-g9w3: Malware in npmresearch2026-prov-test
npmresearch2026-prov-test >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rj9g-592x-g9w3: Malware
- SCA from the title:
GHSA-6hrm-xfrq-h4qh: Malware in metrics-probe-9b4c
metrics-probe-9b4c >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6hrm-xfrq-h4qh: Malware
- SCA from the title:
GHSA-c4v5-qmr8-hq6m: Malware in npmresearch2026-scope-test-b
npmresearch2026-scope-test-b >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c4v5-qmr8-hq6m: Malware
- SCA from the title:
GHSA-6vvv-7q4x-wvgg: Malware in @npmresearch4/utils
@npmresearch4/utils >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6vvv-7q4x-wvgg: Malware
- SCA from the title:
GHSA-vg83-hcp4-5qcc / CVE-2026-75518: DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write
@apireno/domshell < 2.0.8 → 2.0.8
Why tagged?
- SCA from the title:
GHSA-vg83-hcp4-5qcc / CVE-202
- SCA from the title:
GHSA-v4vq-23qw-j3r8: Malware in developmentstelemetry
developmentstelemetry >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v4vq-23qw-j3r8: Malware
- SCA from the title:
GHSA-q2h4-4569-r3g5: Malware in @coframe-gtm/annotations
@coframe-gtm/annotations >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q2h4-4569-r3g5: Malware
- SCA from the title:
GHSA-3hj5-cm6m-jpf4: Malware in yangon
yangon >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3hj5-cm6m-jpf4: Malware
- SCA from the title:
GHSA-rcwx-2hqx-rf6q: Malware in daressalaam
daressalaam >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rcwx-2hqx-rf6q: Malware
- SCA from the title:
GHSA-54f5-j4rj-57cc: Malware in algiers
algiers >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-54f5-j4rj-57cc: Malware
- SCA from the title:
GHSA-mjmq-62f2-6w3p: Malware in jeddah
jeddah >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mjmq-62f2-6w3p: Malware
- SCA from the title:
GHSA-468r-9jxp-wpm5: Malware in ludhiana
ludhiana >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-468r-9jxp-wpm5: Malware
- SCA from the title:
GHSA-g77w-9vf6-gxmm: Malware in harbin
harbin >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-g77w-9vf6-gxmm: Malware
- SCA from the title:
GHSA-x48p-rqgw-jw6f: Malware in ranchi
ranchi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-x48p-rqgw-jw6f: Malware
- SCA from the title:
GHSA-4whv-8gf3-58r7: Malware in nanjing
nanjing >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4whv-8gf3-58r7: Malware
- SCA from the title:
GHSA-9qjw-3x59-9g8p: Malware in budapest
budapest >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9qjw-3x59-9g8p: Malware
- SCA from the title:
GHSA-5cw2-p5pg-92c5: Malware in raipur
raipur >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5cw2-p5pg-92c5: Malware
- SCA from the title:
GHSA-fr2v-c55r-89wm: Malware in ahmedabad
ahmedabad >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-fr2v-c55r-89wm: Malware
- SCA from the title:
GHSA-2w46-mc5m-fj42: Malware in bucharest
bucharest >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2w46-mc5m-fj42: Malware
- SCA from the title:
GHSA-x6c6-38jv-xh6w: Malware in jabalpur
jabalpur >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-x6c6-38jv-xh6w: Malware
- SCA from the title:
GHSA-xw8h-93hj-q8wq: Malware in aurangabad
aurangabad >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xw8h-93hj-q8wq: Malware
- SCA from the title:
GHSA-67rm-mx6j-p72g: Malware in meerut
meerut >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-67rm-mx6j-p72g: Malware
- SCA from the title:
GHSA-5x76-vjm4-f469: Malware in mysore
mysore >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5x76-vjm4-f469: Malware
- SCA from the title:
GHSA-hg6p-gq65-grp4: Malware in dhaka
dhaka >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hg6p-gq65-grp4: Malware
- SCA from the title:
GHSA-7hhj-hhv4-xqcr: Malware in hyderabad
hyderabad >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7hhj-hhv4-xqcr: Malware
- SCA from the title:
GHSA-7pm8-488h-944p: Malware in malaga
malaga >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7pm8-488h-944p: Malware
- SCA from the title:
GHSA-rw4h-xw5g-c7mq: Malware in birmingham
birmingham >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rw4h-xw5g-c7mq: Malware
- SCA from the title:
GHSA-xjhh-6c5p-jq5j: Malware in bakersfield
bakersfield >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xjhh-6c5p-jq5j: Malware
- SCA from the title:
GHSA-2744-9f6f-pwvj: Malware in fortworth
fortworth >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2744-9f6f-pwvj: Malware
- SCA from the title:
GHSA-j7g4-cw2x-q3x8: Malware in sanantonio
sanantonio >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j7g4-cw2x-q3x8: Malware
- SCA from the title:
GHSA-jfpc-fc9q-j73r: Malware in elpaso
elpaso >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jfpc-fc9q-j73r: Malware
- SCA from the title:
GHSA-rrr2-8q34-85xx: Malware in oklahomacity
oklahomacity >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rrr2-8q34-85xx: Malware
- SCA from the title:
GHSA-8575-5pff-xp49: Malware in tabnine
tabnine >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8575-5pff-xp49: Malware
- SCA from the title:
GHSA-6h9x-rjf5-jw55: Malware in requester-lb
requester-lb >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6h9x-rjf5-jw55: Malware
- SCA from the title:
GHSA-448f-g3c2-cq9v: Malware in litecore-lib-ltc
litecore-lib-ltc >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-448f-g3c2-cq9v: Malware
- SCA from the title:
GHSA-2rgp-c9mf-f8q7: Malware in @claudeorg/universal-code-generator
@claudeorg/universal-code-generator >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2rgp-c9mf-f8q7: Malware
- SCA from the title:
GHSA-6g8w-4887-v6p3: Malware in fast-deep-thinking
fast-deep-thinking >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6g8w-4887-v6p3: Malware
- SCA from the title:
GHSA-vw84-96h8-p9rf: Malware in tailwind-keyframe-utils
tailwind-keyframe-utils >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vw84-96h8-p9rf: Malware
- SCA from the title:
GHSA-fwpf-2rwq-r74v: Malware in @devcorelab/postcss-animkit
@devcorelab/postcss-animkit >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-fwpf-2rwq-r74v: Malware
- SCA from the title:
GHSA-7cj4-w2r7-x3q8: Malicious code in react-native-datepickerror (npm)
react-native-datepickerror = 99.9.1 → remove it
Why tagged?
- SCA from the title:
GHSA-7cj4-w2r7-x3q8: Maliciou
- SCA from the title:
GHSA-9h9h-w8h8-rgjm: Malicious code in tajul-avengers-cli (npm)
tajul-avengers-cli = 1.4.1 → remove it
Why tagged?
- SCA from the title:
GHSA-9h9h-w8h8-rgjm: Maliciou
- SCA from the title:
GHSA-v4jp-52hh-9chp: Malicious code in calkyippie (npm)
calkyippie = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-v4jp-52hh-9chp: Maliciou
- SCA from the title:
GHSA-5f9p-65w4-73v8: Malicious code in char-ai-sdk (npm)
char-ai-sdk = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-5f9p-65w4-73v8: Maliciou
- SCA from the title:
GHSA-v32q-85mq-fg78: Malicious code in @lasha_lasha/helper (npm)
@lasha_lasha/helper = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-v32q-85mq-fg78: Maliciou
- SCA from the title:
GHSA-c7gv-mp6p-m8mj: Malicious code in calcultimatetest (npm)
calcultimatetest = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-c7gv-mp6p-m8mj: Maliciou
- SCA from the title:
GHSA-5fv6-9w6w-23xh: Malicious code in @h1stealthy/gh046-npm-transfer-9421a2 (npm)
@h1stealthy/gh046-npm-transfer-9421a2 = 0.0.386387 → remove it | = 0.0.386388 → remove it | = 0.0.95891 → remove it
Why tagged?
- SCA from the title:
GHSA-5fv6-9w6w-23xh: Maliciou
- SCA from the title:
GHSA-9599-44wr-v635: Malicious code in calcurender (npm)
calcurender = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-9599-44wr-v635: Maliciou
- SCA from the title:
GHSA-5f96-rfmm-87m9: Malicious code in character-ai-sdk (npm)
character-ai-sdk = 1.0.1 → remove it | = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-5f96-rfmm-87m9: Maliciou
- SCA from the title:
GHSA-jqg3-3r6r-54f3: Malicious code in @clikwraps/navigate (npm)
@clikwraps/navigate = 99.9.1 → remove it
Why tagged?
- SCA from the title:
GHSA-jqg3-3r6r-54f3: Maliciou
- SCA from the title:
GHSA-q32v-qm2p-gw4w: Malicious code in @basis-theory-elements/api-client (npm)
@basis-theory-elements/api-client = 99.9.1 → remove it
Why tagged?
- SCA from the title:
GHSA-q32v-qm2p-gw4w: Maliciou
- SCA from the title:
GHSA-m5xq-h2p4-962g: Malicious code in @fdcasj_dfew/md-doc-mcp (npm)
@fdcasj_dfew/md-doc-mcp = 1.0.0 → remove it | = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-m5xq-h2p4-962g: Maliciou
- AI Security from the title:
GHSA-m5xq-h2p4-962g: Malicious code in @fdcasj_dfew/md-doc-mcp (npm)
- SCA from the title:
GHSA-mg93-rcxj-ghw9: Malware in nectarinei-notthedevs
nectarinei-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mg93-rcxj-ghw9: Malware
- SCA from the title:
GHSA-qqhv-vvqf-75jp: Malware in kiwimflolb-notthedevs
kiwimflolb-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-qqhv-vvqf-75jp: Malware
- SCA from the title:
GHSA-5mc9-4q86-fv9c: Malware in raspberryf-notthedevs
raspberryf-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5mc9-4q86-fv9c: Malware
- SCA from the title:
GHSA-794v-8p7x-wpvf: Malware in nectarine4-notthedevs
nectarine4-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-794v-8p7x-wpvf: Malware
- SCA from the title:
GHSA-mmxj-fv6x-r4hx: Malware in strawberry-notthedevs
strawberry-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mmxj-fv6x-r4hx: Malware
- SCA from the title:
GHSA-phxh-49fh-gxhm: Malware in lemono0geg-notthedevs
lemono0geg-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-phxh-49fh-gxhm: Malware
- SCA from the title:
GHSA-hfgp-23qj-7vxf: Malware in mangodjbgd-notthedevs
mangodjbgd-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hfgp-23qj-7vxf: Malware
- SCA from the title:
GHSA-m7r5-qm6f-c6q7: Malware in pearx93qja-notthedevs
pearx93qja-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m7r5-qm6f-c6q7: Malware
- SCA from the title:
GHSA-v2qf-6ffc-j86r: Malware in coconutb0o-notthedevs
coconutb0o-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v2qf-6ffc-j86r: Malware
- SCA from the title:
GHSA-2wm4-8qqx-958f: Malware in pearmwr0w0-notthedevs
pearmwr0w0-notthedevs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2wm4-8qqx-958f: Malware
- SCA from the title:
GHSA-6m66-5gxq-w93m: Malware in crypapiapi
crypapiapi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6m66-5gxq-w93m: Malware
- SCA from the title:
GHSA-8hw9-ch78-32cg: Malware in ruby-baileys
ruby-baileys = 0.0.0-stage → remove it | = 1.5.17 → remove it | = 1.5.18 → remove it
Why tagged?
- SCA from the title:
GHSA-8hw9-ch78-32cg: Malware
- SCA from the title:
GHSA-fj3h-g2vc-3fvx: Malware in ndraawzz-baileys
ndraawzz-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-fj3h-g2vc-3fvx: Malware
- SCA from the title:
GHSA-m4p3-qr69-gqjp: Malware in kevinx-baileys
kevinx-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m4p3-qr69-gqjp: Malware
- SCA from the title:
GHSA-69p8-fqvj-5jw8: Malware in itssofc
itssofc >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-69p8-fqvj-5jw8: Malware
- SCA from the title:
GHSA-w5vj-vh52-62wh: Malware in aemeath-baileys
aemeath-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w5vj-vh52-62wh: Malware
- SCA from the title:
GHSA-8gjx-j92q-wfwr: Malware in aemath
aemath >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8gjx-j92q-wfwr: Malware
- SCA from the title:
GHSA-r483-947g-9m35: Malware in @zaxius/baileys
@zaxius/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-r483-947g-9m35: Malware
- SCA from the title:
GHSA-x6g3-r8x5-pjg4: Malware in @wanzforme/bails4u
@wanzforme/bails4u >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-x6g3-r8x5-pjg4: Malware
- SCA from the title:
GHSA-wpq7-r76p-73cp: Malware in @wanzforme/bails
@wanzforme/bails >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wpq7-r76p-73cp: Malware
- SCA from the title:
GHSA-g3g2-5252-hcj5: Malware in @raffnotdev/baileys
@raffnotdev/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-g3g2-5252-hcj5: Malware
- SCA from the title:
GHSA-93hx-h37m-r69f: Malware in @monze1239/baileys
@monze1239/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-93hx-h37m-r69f: Malware
- SCA from the title:
GHSA-wrhf-54qp-qr2j: Malware in @lekzoz/baileys
@lekzoz/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wrhf-54qp-qr2j: Malware
- SCA from the title:
GHSA-cmxr-cgpv-4696: Malware in @lekzsync/baileys
@lekzsync/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cmxr-cgpv-4696: Malware
- SCA from the title:
GHSA-2q5q-m7xg-cp3v: Malware in amlekzo
amlekzo >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2q5q-m7xg-cp3v: Malware
- SCA from the title:
GHSA-5xfm-j5g3-qrw5: Malware in @lekzox/baileys
@lekzox/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5xfm-j5g3-qrw5: Malware
- SCA from the title:
GHSA-gvq9-v7r2-592g: Malware in @dyllxnn/baileys
@dyllxnn/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gvq9-v7r2-592g: Malware
- SCA from the title:
GHSA-4wq5-r4mr-w74h: Malware in @bellaxchan/eleventech
@bellaxchan/eleventech >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4wq5-r4mr-w74h: Malware
- SCA from the title:
GHSA-q8vw-5727-f25r: Malware in @bellaxchan/baileys
@bellaxchan/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q8vw-5727-f25r: Malware
- SCA from the title:
GHSA-h7r5-j6rq-3x29: Malware in @bellaxchan/sixtech
@bellaxchan/sixtech >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h7r5-j6rq-3x29: Malware
- SCA from the title:
GHSA-jxq3-wr67-vjq2: Malware in @bellaxchan/wbails
@bellaxchan/wbails >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jxq3-wr67-vjq2: Malware
- SCA from the title:
GHSA-3mjw-7x59-6gr6: Malware in @bellaxchan/bellaxtech
@bellaxchan/bellaxtech >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3mjw-7x59-6gr6: Malware
- SCA from the title:
GHSA-p99r-cq2r-f4rv: Malware in @bellaxchan/wabails
@bellaxchan/wabails >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-p99r-cq2r-f4rv: Malware
- SCA from the title:
GHSA-7rqm-pfqg-88c9: Malware in @bellaxchan/techxatz
@bellaxchan/techxatz >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7rqm-pfqg-88c9: Malware
- SCA from the title:
GHSA-g5g9-r3pg-wm8w: Malware in @bellaxchan/beltech
@bellaxchan/beltech >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-g5g9-r3pg-wm8w: Malware
- SCA from the title:
GHSA-q695-p99r-xwj7: Malware in @bellaxchan/libsignal-node
@bellaxchan/libsignal-node >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q695-p99r-xwj7: Malware
- SCA from the title:
GHSA-p64q-pg36-qghw: Malware in @bellaxchan/bailtech
@bellaxchan/bailtech >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-p64q-pg36-qghw: Malware
- SCA from the title:
GHSA-xmvq-9f29-fx3w: Malware in @denzz221/baileys
@denzz221/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xmvq-9f29-fx3w: Malware
- SCA from the title:
GHSA-ffr4-pggp-r7cv: Malware in @axo_cuy/baileys
@axo_cuy/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-ffr4-pggp-r7cv: Malware
- SCA from the title:
GHSA-8h3c-p8q4-6cxp: Malware in @axo_cuy/baileyss
@axo_cuy/baileyss >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8h3c-p8q4-6cxp: Malware
- SCA from the title:
GHSA-82w4-rgrf-57v2: Malware in @nuri.yavuz.tr.2/my-unique-pinger
@nuri.yavuz.tr.2/my-unique-pinger >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-82w4-rgrf-57v2: Malware
- SCA from the title:
GHSA-66p6-67hr-9hw7: Malware in requestcatcher-pinger-v2
requestcatcher-pinger-v2 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-66p6-67hr-9hw7: Malware
- SCA from the title:
GHSA-7pqc-wx7c-xrxh: Malware in csv-generatee
csv-generatee >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7pqc-wx7c-xrxh: Malware
- SCA from the title:
GHSA-4926-8w4g-8h5r: Malware in csv-generater
csv-generater >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4926-8w4g-8h5r: Malware
- SCA from the title:
GHSA-h8xq-3qvf-p57g: Malware in teick
teick >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h8xq-3qvf-p57g: Malware
- SCA from the title:
GHSA-3j9x-9vw3-5j8m: Malware in lupedsagaces
lupedsagaces >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3j9x-9vw3-5j8m: Malware
- SCA from the title:
GHSA-9546-39ph-2v3p: Malware in prettier-plugin-solidity-import-order
prettier-plugin-solidity-import-order >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9546-39ph-2v3p: Malware
- SCA from the title:
GHSA-ph54-72p2-732v: Malware in tajul-avengers
tajul-avengers >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-ph54-72p2-732v: Malware
- SCA from the title:
GHSA-2m9m-6cr5-9x25 / CVE-2026-63129: mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses
@connorbritain/mssql-mcp-core <= 0.5.0 → 0.6.0; @connorbritain/mssql-mcp-reader <= 0.4.2 → 0.5.0; @connorbritain/mssql-mcp-writer <= 0.4.2 → 0.5.0; @connorbritain/mssql-mcp-server <= 0.5.2 → 0.6.0
Why tagged?
- SCA from the title:
GHSA-2m9m-6cr5-9x25 / CVE-202
- AI Security from the title:
/ CVE-2026-63129: mssql-mcp-core: SQL injection in mssql-mcp write t
- SCA from the title:
GHSA-mr2f-4c3p-9j9w: Malware in rmraf
rmraf >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mr2f-4c3p-9j9w: Malware
- SCA from the title:
GHSA-h279-4vg6-3c75: Malware in react-r2d2
react-r2d2 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h279-4vg6-3c75: Malware
- SCA from the title:
GHSA-j46w-5jjm-pqc5: Malware in temporary-uploader
temporary-uploader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j46w-5jjm-pqc5: Malware
- SCA from the title:
GHSA-wgc3-6gfq-5483: Malware in @mrnima/tiktok-downloader
@mrnima/tiktok-downloader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wgc3-6gfq-5483: Malware
- SCA from the title:
GHSA-6x86-fc9w-xp6x: Malware in @mrnima/technology_news_info
@mrnima/technology_news_info >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6x86-fc9w-xp6x: Malware
- SCA from the title:
GHSA-5pcf-6xmr-rc94: Malware in arenaev-vehicles-news
arenaev-vehicles-news >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5pcf-6xmr-rc94: Malware
- SCA from the title:
GHSA-795h-8j3r-r625: Malware in @mrnima/facebook-downloader
@mrnima/facebook-downloader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-795h-8j3r-r625: Malware
- SCA from the title:
GHSA-xpg9-wrj3-hr45: Malware in @mrnima/instagram-downloader
@mrnima/instagram-downloader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xpg9-wrj3-hr45: Malware
- SCA from the title:
GHSA-qvgp-56r2-v2q2: Malware in mrnima-moviedl
mrnima-moviedl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-qvgp-56r2-v2q2: Malware
- SCA from the title:
GHSA-548m-8xp5-jgp2: Malware in sinhala-cricket-newsjs
sinhala-cricket-newsjs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-548m-8xp5-jgp2: Malware
- SCA from the title:
GHSA-jhfv-qmvr-xmhf: Malware in mrnima-fbdl
mrnima-fbdl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jhfv-qmvr-xmhf: Malware
- SCA from the title:
GHSA-45m5-7r63-4q29: Malware in node-json-manager
node-json-manager >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-45m5-7r63-4q29: Malware
- SCA from the title:
GHSA-696j-fr5c-8x43: Malware in @mrnima/local-database-manager
@mrnima/local-database-manager >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-696j-fr5c-8x43: Malware
- SCA from the title:
GHSA-9phf-hr2g-vj75: Malware in mrnima-temporary-uploader
mrnima-temporary-uploader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9phf-hr2g-vj75: Malware
- SCA from the title:
GHSA-f46p-hww7-5hvm: Malware in pastebin-reup
pastebin-reup >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f46p-hww7-5hvm: Malware
- SCA from the title:
GHSA-2r74-q8jf-4jj5: Malware in @mrnima/wabetainfo
@mrnima/wabetainfo >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2r74-q8jf-4jj5: Malware
- SCA from the title:
GHSA-9xg6-v4wj-vr3v: Malware in gms-mobile-news
gms-mobile-news >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9xg6-v4wj-vr3v: Malware
- SCA from the title:
GHSA-m2w3-5xf7-5hrc: Malware in nima_maker
nima_maker >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m2w3-5xf7-5hrc: Malware
- SCA from the title:
GHSA-w93h-mf3h-5wrv: Malware in tech-news-scraper
tech-news-scraper >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w93h-mf3h-5wrv: Malware
- SCA from the title:
GHSA-r2g7-mv2c-m8q2: Malware in nima-google-now
nima-google-now >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-r2g7-mv2c-m8q2: Malware
- SCA from the title:
GHSA-hjwj-h3jp-gqfg: Malware in nima-wabeta-info
nima-wabeta-info >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hjwj-h3jp-gqfg: Malware
- SCA from the title:
GHSA-w2v7-cv8x-mh7x: Malware in mrnima-baileys
mrnima-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w2v7-cv8x-mh7x: Malware
- SCA from the title:
GHSA-hf65-h9jm-8xxw: Malware in photo-video-uploader
photo-video-uploader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hf65-h9jm-8xxw: Malware
- SCA from the title:
GHSA-8988-hh4f-r8vv: Malware in elisa_module
elisa_module >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8988-hh4f-r8vv: Malware
- SCA from the title:
GHSA-qf7h-7m7w-6vrm: Malware in nima-threads-dl-api
nima-threads-dl-api >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-qf7h-7m7w-6vrm: Malware
- SCA from the title:
GHSA-j4m9-fr6w-9996: Malware in queen-elisa-sticker-maker
queen-elisa-sticker-maker >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j4m9-fr6w-9996: Malware
- SCA from the title:
GHSA-xvx7-m3mm-3jpw: Malware in mrnima-openai-chatgpt-bot
mrnima-openai-chatgpt-bot >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xvx7-m3mm-3jpw: Malware
- SCA from the title:
GHSA-f95c-6jc7-wwvq: Malware in elisa_downloader
elisa_downloader >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f95c-6jc7-wwvq: Malware
- SCA from the title:
GHSA-8qfh-wjm9-48gh: Malware in ios-news
ios-news >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8qfh-wjm9-48gh: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
11 Go security advisories
GHSA-m932-63jc-4jqq / CVE-2026-130007: k8s-mcp-server: Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution
github.com/reza-gholizade/k8s-mcp-server < 1.1.0 → 1.1.0
Why tagged?
- SCA from the title:
GHSA-m932-63jc-4jqq / CVE-202
- AI Security from the title:
/ CVE-2026-130007: k8s-mcp-server: Missing authentication on default SSE/HTTP tra
- SCA from the title:
GHSA-vwhp-8p66-mq4f / CVE-2026-95839: containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
github.com/containerd/containerd/v2 >= 2.2.0, < 2.2.10 → 2.2.10 | >= 2.3.0, < 2.3.7 → 2.3.7 | >= 2.4.0, < 2.4.2 → 2.4.2
Why tagged?
- SCA from the title:
GHSA-vwhp-8p66-mq4f / CVE-202
- SCA from the title:
GHSA-7rj6-7pqx-v7rm / CVE-2026-121717: fzf: Predictable FIFO path in zsh completion allows local symlink attack / arbitrary file overwrite as the victim user (_fzf_feed_fifo)
github.com/junegunn/fzf <= 0.74.4 → 0.74.5
Why tagged?
- SCA from the title:
GHSA-7rj6-7pqx-v7rm / CVE-202
- SCA from the title:
GHSA-w6x2-f5m4-xw82 / CVE-2026-121716: fzf: Arbitrary command execution via bash arithmetic expansion on unvalidated layout size in fzf-tmux (-l/-u attached value)
github.com/junegunn/fzf <= 0.74.4 → 0.74.5
Why tagged?
- SCA from the title:
GHSA-w6x2-f5m4-xw82 / CVE-202
- SCA from the title:
GHSA-q433-mp6c-8v4f / CVE-2026-130008: sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table
github.com/StacklokLabs/sqlite-mcp < 0.1.2 → 0.1.2
Why tagged?
- SCA from the title:
GHSA-q433-mp6c-8v4f / CVE-202
- AI Security from the title:
CVE-2026-130008: sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table
- SCA from the title:
GHSA-5hj8-q7fv-qrj6 / CVE-2026-128073: gosaml2: Unauthenticated panic decrypting an EncryptedAssertion with a short or empty CipherValue
github.com/russellhaering/gosaml2 <= 0.11.0 → 0.12.0
Why tagged?
- SCA from the title:
GHSA-5hj8-q7fv-qrj6 / CVE-202
- SCA from the title:
GHSA-w42c-h7hr-f67p / CVE-2026-62964: Gortex: Arbitrary file write / repo-confinement escape in `write_file` / `edit_file` / `move_inline` MCP tools → code execution
github.com/zzet/gortex < 0.55.0 → 0.55.0
Why tagged?
- SCA from the title:
GHSA-w42c-h7hr-f67p / CVE-202
- SCA from the title:
GHSA-j282-pjg5-j643 / CVE-2026-76101: keystore-go: Keystore integrity and password verification bypass via stripped trailing digest in Decode()
github.com/pavel-v-chernykh/keystore-go <= 2.1.0 → no fix; github.com/pavel-v-chernykh/keystore-go/v3 < 3.0.0 → 3.0.0 · partly fixed
Why tagged?
- SCA from the title:
GHSA-j282-pjg5-j643 / CVE-202
- SCA from the title:
GHSA-4g68-3pwx-5vfj / CVE-2026-58214: NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata
github.com/nats-io/nats-server/v2 < 2.12.12 → 2.12.12 | >= 2.14.0-RC.1, < 2.14.3 → 2.14.3
Why tagged?
- SCA from the title:
GHSA-4g68-3pwx-5vfj / CVE-202
- SCA from the title:
GHSA-qrcv-3558-gj4f / CVE-2026-58213: NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection
github.com/nats-io/nats-server/v2 < 2.12.9 → 2.12.9 | >= 2.14.0-RC.1, < 2.14.1 → 2.14.1
Why tagged?
- SCA from the title:
GHSA-qrcv-3558-gj4f / CVE-202
- SCA from the title:
GHSA-8fh7-7q4q-cq52 / CVE-2026-75521: Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
miren.dev/runtime < 0.11.1 → 0.11.1
Why tagged?
- SCA from the title:
GHSA-8fh7-7q4q-cq52 / CVE-202
- SCA from the title:
All Go advisories · each advisory is independent, not one campaign
2 Multi-ecosystem security advisories
GHSA-3mgh-93r5-r7jf / CVE-2026-83816: CodeWhale: exec_shell parallel-readonly classifier auto-approves fd/rg/git grep exec flags enabling silent RCE
codewhale-tui <= 0.8.67 → 0.9.0; codewhale <= 0.8.67 → 0.9.0
Why tagged?
- SCA from the title:
GHSA-3mgh-93r5-r7jf / CVE-202
- SCA from the title:
GHSA-8hp3-xxrg-v9c8 / CVE-2026-83817: CodeWhale: Automation auto_approve defaults to true, bypassing the task-path hardening fix for silent recurring agent execution
codewhale-tui <= 0.8.67 → 0.9.0; codewhale <= 0.8.67 → 0.9.0
Why tagged?
- SCA from the title:
GHSA-8hp3-xxrg-v9c8 / CVE-202
- SCA from the title:
All Multi-ecosystem advisories · each advisory is independent, not one campaign
GHSA-f3mh-rxg3-f5g2 / CVE-2026-119346: Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
next >= 15.0.0, <= 15.5.28 → 15.5.29 | >= 16.0.0, <= 16.4.4 → 16.4.5
Why tagged?
- SCA from the title:
GHSA-f3mh-rxg3-f5g2 / CVE-202
- SCA from the title:
GHSA-7qx7-33qx-rqx2 / CVE-2026-119347: Next.js: SVG rejection bypass in the image optimization
next >= 15.0.0, <= 15.5.28 → 15.5.29 | >= 16.0.0, <= 16.4.4 → 16.4.5
Why tagged?
- SCA from the title:
GHSA-7qx7-33qx-rqx2 / CVE-202
- SCA from the title:
GHSA-pc58-hwjq-p385 / CVE-2026-119348: Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
next >= 16.0.0, <= 16.4.4 → 16.4.5 | <= 15.5.28 → 15.5.29
Why tagged?
- SCA from the title:
GHSA-pc58-hwjq-p385 / CVE-202
- SCA from the title:
GHSA-rhh4-g77r-r9qj / CVE-2026-119349: Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
next >= 16.0.0, <= 16.4.4 → 16.4.5
Why tagged?
- SCA from the title:
GHSA-rhh4-g77r-r9qj / CVE-202
- SCA from the title:
GHSA-vvgp-ww4w-46vf / CVE-2026-119350: Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
next >= 16.4.0, <= 16.4.4 → 16.4.5
Why tagged?
- SCA from the title:
GHSA-vvgp-ww4w-46vf / CVE-202
- SCA from the title:
2 NuGet security advisories
GHSA-464h-4j8h-q5mf / CVE-2026-102529: HtmlSanitizer: CSS Removal DoS
HtmlSanitizer < 9.0.967 → 9.0.967 | >= 9.1.878-beta, < 9.1.968-beta → 9.1.968-beta
Why tagged?
- SCA from the title:
GHSA-464h-4j8h-q5mf / CVE-202
- SCA from the title:
GHSA-3h63-w8jq-rrf2 / CVE-2026-59975: SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service
SharpIppNext <= 4.0.2 → 4.1.0
Why tagged?
- SCA from the title:
GHSA-3h63-w8jq-rrf2 / CVE-202
- SCA from the title:
All NuGet advisories · each advisory is independent, not one campaign
6 RubyGems security advisories
GHSA-h5m9-42h9-vcq6 / CVE-2026-115472: Doorkeeper: When using public clients, any client can revoke any access token
doorkeeper < 5.9.1 → 5.9.1
Why tagged?
- SCA from the title:
GHSA-h5m9-42h9-vcq6 / CVE-202
- SCA from the title:
GHSA-cpg3-jjwc-f9qx: Malicious code in secretlens (RubyGems)
secretlens = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-cpg3-jjwc-f9qx: Maliciou
- SCA from the title:
GHSA-w9cm-wm83-69r3: Malicious code in fh-skeleton-web (RubyGems)
fh-skeleton-web = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-w9cm-wm83-69r3: Maliciou
- SCA from the title:
GHSA-93rp-j336-vgfm: Malicious code in gmo-payment-carrier (RubyGems)
gmo-payment-carrier = 0.0.99 → remove it
Why tagged?
- SCA from the title:
GHSA-93rp-j336-vgfm: Maliciou
- SCA from the title:
GHSA-6c5q-63v2-x3j2: Malicious code in gmo-payment (RubyGems)
gmo-payment = 0.0.99 → remove it
Why tagged?
- SCA from the title:
GHSA-6c5q-63v2-x3j2: Maliciou
- SCA from the title:
GHSA-37qj-58qv-vjrv: Malicious code in aws_sdk_wrapper (RubyGems)
aws_sdk_wrapper = 0.0.99 → remove it
Why tagged?
- SCA from the title:
GHSA-37qj-58qv-vjrv: Maliciou
- SCA from the title:
All RubyGems advisories · each advisory is independent, not one campaign
5 Maven security advisories
GHSA-w3w6-9m25-g88p / CVE-2026-109549: OmniFaces: SSE push channels are not bound to their owning HTTP session
org.omnifaces:omnifaces >= 5.2.0, <= 5.4.2 → 5.4.3
Why tagged?
- SCA from the title:
GHSA-w3w6-9m25-g88p / CVE-202
- SCA from the title:
GHSA-jmmc-wjpc-pg34 / CVE-2026-61689: XWiki Platform: HQL injection in search allows unauthenticated database extraction including password hashes
org.xwiki.platform:xwiki-platform-rest-server >= 4.3-milestone-1, < 16.10.18 → 16.10.18 | >= 18.0.0-rc-1, < 18.2.0 → 18.2.0 | >= 17.0.0-rc-1, < 17.10.5 → 17.10.5
Why tagged?
- SCA from the title:
GHSA-jmmc-wjpc-pg34 / CVE-202
- SCA from the title:
GHSA-gpcc-36pq-8qxr / CVE-2026-76090: Tapir: Construction/decode RCE via property name -> raw case-class field (tapir-openapi-codegen)
com.softwaremill.sttp.tapir:tapir-openapi-codegen-core < 1.13.27 → 1.13.27
Why tagged?
- SCA from the title:
GHSA-gpcc-36pq-8qxr / CVE-202
- SCA from the title:
GHSA-cvx8-9ff6-54xq / CVE-2026-76088: PGPainless: Unbounded Compressed Packet Descent in inline-detach and MessageInspector leads to Denial of Service (DoS)
org.pgpainless:pgpainless-core < 1.7.8 → 1.7.8 | >= 2.0.0, < 2.0.4 → 2.0.4
Why tagged?
- SCA from the title:
GHSA-cvx8-9ff6-54xq / CVE-202
- SCA from the title:
GHSA-jc42-994r-vvwp / CVE-2026-73504: cassandra-jdbc-wrapper: Authentication Token Exposed in Logs
com.ing.data:cassandra-jdbc-wrapper >= 5.0.0, < 5.0.2 → 5.0.2 | <= 4.16.3 → 4.16.4
Why tagged?
- SCA from the title:
GHSA-jc42-994r-vvwp / CVE-202
- SCA from the title:
All Maven advisories · each advisory is independent, not one campaign
4 Packagist security advisories
GHSA-mqwx-84vv-mp26 / CVE-2026-63193: October: Media Library Crop Handler Bypasses Upload Extension Allowlist
october/october <= 3.7.13 → no fix | >= 4.0.0, <= 4.3.1 → 4.3.2 · partly fixed
Why tagged?
- SCA from the title:
GHSA-mqwx-84vv-mp26 / CVE-202
- SCA from the title:
GHSA-q8v2-3j4h-xg2p / CVE-2026-63412: Jane: Instantiation RCE via query parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
jane-php/open-api-3 < 7.12.0 → 7.12.0
Why tagged?
- SCA from the title:
GHSA-q8v2-3j4h-xg2p / CVE-202
- SCA from the title:
GHSA-x9xr-53qx-9qcf / CVE-2026-63413: Jane: Instantiation RCE via header parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
jane-php/open-api-3 < 7.12.0 → 7.12.0
Why tagged?
- SCA from the title:
GHSA-x9xr-53qx-9qcf / CVE-202
- SCA from the title:
GHSA-xwcw-j52r-34x4 / CVE-2026-63411: Jane: Instantiation RCE via parameter description -> raw PHPDoc */ breakout (jane-php/open-api-3)
jane-php/open-api-3 < 7.12.0 → 7.12.0
Why tagged?
- SCA from the title:
GHSA-xwcw-j52r-34x4 / CVE-202
- SCA from the title:
All Packagist advisories · each advisory is independent, not one campaign
2 crates.io security advisories
GHSA-pxh3-4qqv-58mg / CVE-2026-61713: Servo Sandbox bypass: declarative refresh can auto-navigate a sandboxed iframe
servo < 0.3.0 → 0.3.0
Why tagged?
- SCA from the title:
GHSA-pxh3-4qqv-58mg / CVE-202
- SCA from the title:
GHSA-59c6-w34f-h244: Malicious code in besk (crates.io)
besk = 0.1.1 → remove it
Why tagged?
- SCA from the title:
GHSA-59c6-w34f-h244: Maliciou
- SCA from the title:
All crates.io advisories · each advisory is independent, not one campaign
Ruby2Shell: critical Ruby RCE, affected versions and how to fix it (GHSA-34m4-m9fh-gqp5)
Ruby2Shell is a critical Ruby flaw that can give attackers code execution. See affected versions, whether GitLab is hit, and how to upgrade and fix it. Category: Vulnerabilities & Threats
SCARVA: Interpretable Agentic Reasoning in Software Supply-Chain Analysis
Complex applications may inherit security vulnerabilities from their dependencies, though a vulnerable dependency does not necessarily endanger the application. Existing tools flag dependencies associated with public vulnerabilities, and more advanced ones analyze the call…
Why tagged?
- SCA from the title:
le Agentic Reasoning in Software Supply-Chain Analysis
- SCA from the title:
45 npm security advisories
GHSA-r5wx-3c8c-ccxm: Malware in onecode-linux-x64
onecode-linux-x64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-r5wx-3c8c-ccxm: Malware
- SCA from the title:
GHSA-w94w-q524-wgvr: Malware in @onescience/onecode
@onescience/onecode >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w94w-q524-wgvr: Malware
- SCA from the title:
GHSA-hmx8-gj8r-q3g8: Malware in @onescience/onecode-web
@onescience/onecode-web >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hmx8-gj8r-q3g8: Malware
- SCA from the title:
GHSA-cqr8-874q-2g4r: Malware in create-saint
create-saint >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cqr8-874q-2g4r: Malware
- SCA from the title:
GHSA-88q3-gch3-5396 / CVE-2026-73864: install-artifact-from-github loads downloaded native artifacts without integrity verification
install-artifact-from-github <= 1.6.0 → 1.7.0
Why tagged?
- SCA from the title:
GHSA-88q3-gch3-5396 / CVE-202
- SCA from the title:
GHSA-gx35-phhv-wc8w: Malware in nodetokyo
nodetokyo >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gx35-phhv-wc8w: Malware
- SCA from the title:
GHSA-mjg5-fmpm-vgfv: Malware in expresstokyo
expresstokyo >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mjg5-fmpm-vgfv: Malware
- SCA from the title:
GHSA-7jvc-9xq8-frff / CVE-2026-71425: Outstatic: Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins
outstatic <= 2.2.0 → 2.2.1
Why tagged?
- SCA from the title:
GHSA-7jvc-9xq8-frff / CVE-202
- SCA from the title:
GHSA-f4pf-fffj-pv2f: Malware in abiba-avi-aumaunnaaa
abiba-avi-aumaunnaaa = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-f4pf-fffj-pv2f: Malware
- SCA from the title:
GHSA-xr82-65pq-hwqf: Malware in abiba-avbai-ayub
abiba-avbai-ayub = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-xr82-65pq-hwqf: Malware
- SCA from the title:
GHSA-x524-w3hq-7h99: Malware in ahmad-basikal
ahmad-basikal = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-x524-w3hq-7h99: Malware
- SCA from the title:
GHSA-266h-2r44-vrfv: Malware in adnanyahya
adnanyahya = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-266h-2r44-vrfv: Malware
- SCA from the title:
GHSA-24fx-2xw3-w835: Malware in adnanwaleed
adnanwaleed = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-24fx-2xw3-w835: Malware
- SCA from the title:
GHSA-jhvj-53fv-pm4q: Malware in administrative_lark_replicate_automation
administrative_lark_replicate_automation = 2.4.2 → remove it
Why tagged?
- SCA from the title:
GHSA-jhvj-53fv-pm4q: Malware
- SCA from the title:
GHSA-85cw-8h66-5jfr: Malware in adiwibowo
adiwibowo = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-85cw-8h66-5jfr: Malware
- SCA from the title:
GHSA-q7vw-jfcf-5h62: Malware in adilnabeel
adilnabeel = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-q7vw-jfcf-5h62: Malware
- SCA from the title:
GHSA-qfc8-px48-xx9p: Malware in adilfaheem
adilfaheem = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-qfc8-px48-xx9p: Malware
- SCA from the title:
GHSA-rp45-vmj7-729c: Malware in abia-avugi-anina
abia-avugi-anina = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-rp45-vmj7-729c: Malware
- SCA from the title:
GHSA-8rm4-r7pm-8v9r: Malware in aamirhafiz
aamirhafiz = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-8rm4-r7pm-8v9r: Malware
- SCA from the title:
GHSA-gq2c-q5xr-rfpv: Malware in @zakir300408/wechat-companion
@zakir300408/wechat-companion = 0.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-gq2c-q5xr-rfpv: Malware
- SCA from the title:
GHSA-8x6x-x6v6-434r: Malware in @merceas/anchor
@merceas/anchor >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8x6x-x6v6-434r: Malware
- SCA from the title:
GHSA-9pjm-78xx-c2pq: Malware in @merceas/rpc-websockets
@merceas/rpc-websockets >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9pjm-78xx-c2pq: Malware
- SCA from the title:
GHSA-pc7w-ch55-9pff: Malware in @merceas/cross-fetch
@merceas/cross-fetch >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pc7w-ch55-9pff: Malware
- SCA from the title:
GHSA-2w6h-pw36-42xm: Malware in @tobyvalk123/tixte
@tobyvalk123/tixte >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2w6h-pw36-42xm: Malware
- SCA from the title:
GHSA-xvcc-vqjv-phqh / CVE-2026-63496: augment-virShell allows Command Injection in `grep()` via Unsanitized `searchPattern`
@augment-vir/node < 31.73.5 → 31.73.5
Why tagged?
- SCA from the title:
GHSA-xvcc-vqjv-phqh / CVE-202
- SCA from the title:
GHSA-9q69-8j7m-ppmh: Malware in qrcode-reader-vue3
qrcode-reader-vue3 = 3.1.4 → remove it
Why tagged?
- SCA from the title:
GHSA-9q69-8j7m-ppmh: Malware
- SCA from the title:
GHSA-pjx5-g5xc-q286: Malware in react-cache-hook
react-cache-hook >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pjx5-g5xc-q286: Malware
- SCA from the title:
GHSA-xm7q-cc2p-j7w8: Malware in cortico-world-see-now
cortico-world-see-now = 0.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-xm7q-cc2p-j7w8: Malware
- SCA from the title:
GHSA-w94f-fcwx-g3h2: Malware in @cutehttp/encode-url
@cutehttp/encode-url >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w94f-fcwx-g3h2: Malware
- SCA from the title:
GHSA-q2gg-hx87-cj97: Malware in @cutehttp/strict-uri-encode
@cutehttp/strict-uri-encode >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q2gg-hx87-cj97: Malware
- SCA from the title:
GHSA-vv85-jxhh-6fhc: Malware in fiddle-js
fiddle-js >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vv85-jxhh-6fhc: Malware
- SCA from the title:
GHSA-4g5f-v2qx-j2qp: Malware in jest-test
jest-test >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4g5f-v2qx-j2qp: Malware
- SCA from the title:
GHSA-xrvx-xq53-6q5c: Malware in stellar-api-safe
stellar-api-safe >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xrvx-xq53-6q5c: Malware
- SCA from the title:
GHSA-x5g6-2wvp-v57q: Malware in stellar-api-core
stellar-api-core >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-x5g6-2wvp-v57q: Malware
- SCA from the title:
GHSA-j475-jg98-766v: Malware in @nexoratechorg/postcss-keyframes
@nexoratechorg/postcss-keyframes >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j475-jg98-766v: Malware
- SCA from the title:
GHSA-jqf4-9m2v-868j: Malware in tailwindcss-animation-suite
tailwindcss-animation-suite >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jqf4-9m2v-868j: Malware
- SCA from the title:
GHSA-4gmp-923c-272f: Malicious code in canvas_webgl_minimal (npm)
canvas_webgl_minimal = 11.11.13 → remove it
Why tagged?
- SCA from the title:
GHSA-4gmp-923c-272f: Maliciou
- SCA from the title:
GHSA-qvr6-fh5r-q4rj: Malicious code in playwright-config (npm)
playwright-config = 20.20.20 → remove it
Why tagged?
- SCA from the title:
GHSA-qvr6-fh5r-q4rj: Maliciou
- SCA from the title:
GHSA-wfcr-g5w9-97gc: Malicious code in base62-85x (npm)
base62-85x = 5.0.4 → remove it
Why tagged?
- SCA from the title:
GHSA-wfcr-g5w9-97gc: Maliciou
- SCA from the title:
GHSA-vhg4-83fq-5qrp: Malicious code in base128-x58-1 (npm)
base128-x58-1 = 0.0.1 → remove it | = 0.0.2 → remove it | = 0.0.3 → remove it | = 0.0.4 → remove it
Why tagged?
- SCA from the title:
GHSA-vhg4-83fq-5qrp: Maliciou
- SCA from the title:
GHSA-r528-47jm-jff4: Malicious code in @clickwraps/fetch (npm)
@clickwraps/fetch = 99.9.1 → remove it
Why tagged?
- SCA from the title:
GHSA-r528-47jm-jff4: Maliciou
- SCA from the title:
GHSA-j2hq-r459-pg6f: Malicious code in vant (npm)
vant = 2.13.3 → remove it | = 2.13.4 → remove it | = 2.13.5 → remove it | = 3.6.13 → remove it | = 3.6.14 → remove it | = 3.6.15 → remove it; +4 more
Why tagged?
- SCA from the title:
GHSA-j2hq-r459-pg6f: Maliciou
- SCA from the title:
GHSA-j6rp-v2x9-m5rw: Malware in apintergrationpost
apintergrationpost >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j6rp-v2x9-m5rw: Malware
- SCA from the title:
GHSA-fv82-jh67-xx7q: Malware in @tnhorg/agent-skills
@tnhorg/agent-skills >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-fv82-jh67-xx7q: Malware
- SCA from the title:
GHSA-m5wx-ph7h-3vhf: Malware in a-sub-watcher
a-sub-watcher >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m5wx-ph7h-3vhf: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
3 Go security advisories
GHSA-vc6p-m6vx-6cwq / CVE-2026-75506: OliveTin: Second-Order OS Command Injection via shellAfterCompleted
github.com/OliveTin/OliveTin < 0.0.0-20260728155752-e5d29b68da66 → 0.0.0-20260728155752-e5d29b68da66
Why tagged?
- SCA from the title:
GHSA-vc6p-m6vx-6cwq / CVE-202
- SCA from the title:
GHSA-jw3m-8q7m-f35r / CVE-2026-68903: LLMKube: Arbitrary Host File Read via Model.spec.source hostPath Injection
github.com/defilantech/llmkube <= 0.8.28 → 0.9.0
Why tagged?
- SCA from the title:
GHSA-jw3m-8q7m-f35r / CVE-202
- SCA from the title:
GHSA-wq26-3j2m-4hvv / CVE-2026-71861: Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
chainguard.dev/sdk <= 0.1.106 → 0.1.107
Why tagged?
- SCA from the title:
GHSA-wq26-3j2m-4hvv / CVE-202
- SCA from the title:
All Go advisories · each advisory is independent, not one campaign
15 PyPI security advisories
GHSA-fq8c-cf54-787p: Malicious code in anchorpy-utils (PyPI)
anchorpy-utils = 1.98.2 → remove it
Why tagged?
- SCA from the title:
GHSA-fq8c-cf54-787p: Maliciou
- SCA from the title:
GHSA-xcrh-m987-2gc7: Malicious code in solana-utils-terminalmoney1 (PyPI)
solana-utils-terminalmoney1 = 1.98.2 → remove it | = 1.98.3 → remove it
Why tagged?
- SCA from the title:
GHSA-xcrh-m987-2gc7: Maliciou
- SCA from the title:
GHSA-5f4r-g88f-gvwq: Malicious code in solana-py-utils (PyPI)
solana-py-utils = 1.98.2 → remove it | = 1.98.3 → remove it
Why tagged?
- SCA from the title:
GHSA-5f4r-g88f-gvwq: Maliciou
- SCA from the title:
GHSA-vf85-8ff2-3r9w / CVE-2026-69131: django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions
django-filer <= 3.4.4 → 3.5.0
Why tagged?
- SCA from the title:
GHSA-vf85-8ff2-3r9w / CVE-202
- SCA from the title:
GHSA-5g9x-qwh5-33x4 / CVE-2026-69138: djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization
djangocms-versioning <= 2.6.0 → 2.6.1
Why tagged?
- SCA from the title:
GHSA-5g9x-qwh5-33x4 / CVE-202
- SCA from the title:
GHSA-3qjx-3879-f59j: Malicious code in qimsdk-app-builder (PyPI)
qimsdk-app-builder = 0.0.0 → remove it | = 0.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-3qjx-3879-f59j: Maliciou
- SCA from the title:
GHSA-m454-f968-8mm6: Malicious code in robloxapiaccess (PyPI)
robloxapiaccess = 0.0.1 → remove it | = 0.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-m454-f968-8mm6: Maliciou
- SCA from the title:
GHSA-53f3-fr3w-q637: Malicious code in libide (PyPI)
libide = 0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-53f3-fr3w-q637: Maliciou
- SCA from the title:
GHSA-28jx-3vgf-w5vr: Malicious code in setnetwork (PyPI)
setnetwork = 0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-28jx-3vgf-w5vr: Maliciou
- SCA from the title:
GHSA-wv8m-qjx2-frc6: Malicious code in quick-telegram-sender (PyPI)
quick-telegram-sender = 0.7 → remove it
Why tagged?
- SCA from the title:
GHSA-wv8m-qjx2-frc6: Maliciou
- SCA from the title:
GHSA-qrhw-9vgf-g3g4: Malicious code in libidreq (PyPI)
libidreq = 0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-qrhw-9vgf-g3g4: Maliciou
- SCA from the title:
GHSA-q6j5-5xjf-4vc7: Malicious code in test23414234234 (PyPI)
test23414234234 = 0.6 → remove it
Why tagged?
- SCA from the title:
GHSA-q6j5-5xjf-4vc7: Maliciou
- SCA from the title:
GHSA-ppjj-9v2m-rqrg: Malicious code in aeivasta (PyPI)
aeivasta = 0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-ppjj-9v2m-rqrg: Maliciou
- SCA from the title:
GHSA-wffj-527j-c4gj: Malicious code in gguf-accelerator (PyPI)
gguf-accelerator = 0.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-wffj-527j-c4gj: Maliciou
- SCA from the title:
GHSA-764m-3ppc-5m73: Malicious code in agent-framework (PyPI)
agent-framework = 1.26.2 → remove it | = 1.26.1 → remove it
Why tagged?
- SCA from the title:
GHSA-764m-3ppc-5m73: Maliciou
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
3 RubyGems security advisories
GHSA-q63g-8phq-pcj6: Malicious code in rechargeapps (RubyGems)
rechargeapps = 999.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-q63g-8phq-pcj6: Maliciou
- SCA from the title:
GHSA-5hrj-7fc3-cmx9 / CVE-2026-130001: Mustache for Ruby: RCE using built-in method access
mustache <= 1.1.2 → 1.1.3
Why tagged?
- SCA from the title:
GHSA-5hrj-7fc3-cmx9 / CVE-202
- SCA from the title:
GHSA-fcw8-r3p6-3gcc: Malicious code in vuln-app (RubyGems)
vuln-app = 1.2.1 → remove it
Why tagged?
- SCA from the title:
GHSA-fcw8-r3p6-3gcc: Maliciou
- SCA from the title:
All RubyGems advisories · each advisory is independent, not one campaign
1 Packagist security advisory
GHSA-82w8-65qw-gch6 / CVE-2026-71481: ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent
altcha-org/altcha >= 2.0.0, < 2.0.3 → 2.0.3
Why tagged?
- SCA from the title:
GHSA-82w8-65qw-gch6 / CVE-202
- SCA from the title:
All Packagist advisories · each advisory is independent, not one campaign
5 crates.io security advisories
GHSA-ff87-73jp-f3v4 / CVE-2026-69158: Atomic Server: Unauthenticated full-response SSRF in Atomic-Server /bookmark endpoint
atomic-server <= 0.40.1 → no fix
Why tagged?
- SCA from the title:
GHSA-ff87-73jp-f3v4 / CVE-202
- SCA from the title:
GHSA-pfwx-xjp4-qxcj / CVE-2026-69157: Atomic Server: Unauthenticated `/setup` invite grants write access to the entire Drive
atomic-server >= 0.29.0, <= 0.40.1 → no fix
Why tagged?
- SCA from the title:
GHSA-pfwx-xjp4-qxcj / CVE-202
- SCA from the title:
GHSA-8vc4-8hjq-988p / CVE-2026-69156: Atomic Server: Arbitrary file read via user-controlled `internalId` in the `/download` handler (leaks root agent private key)
atomic-server >= 0.30.0, <= 0.40.1 → no fix
Why tagged?
- SCA from the title:
GHSA-8vc4-8hjq-988p / CVE-202
- SCA from the title:
GHSA-x277-3wcg-g9r2 / CVE-2026-69155: Atomic Server: Stored XSS via uploaded files served inline (same-origin) on `/download` → account takeover
atomic-server >= 0.30.0, <= 0.40.1 → no fix
Why tagged?
- SCA from the title:
GHSA-x277-3wcg-g9r2 / CVE-202
- SCA from the title:
GHSA-265x-v3qf-ff6p / CVE-2026-61618: snark-verifier accepts non-canonical KZG accumulator limb encodings
snark-verifier < 0.2.5 → 0.2.5
Why tagged?
- SCA from the title:
GHSA-265x-v3qf-ff6p / CVE-202
- SCA from the title:
All crates.io advisories · each advisory is independent, not one campaign
Microsoft agent-framework Compromised: Credential Stealer Targets Azure and CI Pipelines
On November 17, 2026 at 20:35 UTC, versions 1.26.1 & 1.26.2 of the Microsoft PyPI package agent-framework were published with an added credential stealer. The package gets almost 200k downloads a month. The malicious versions have since been quarantined.
Why tagged?
- SCA from the excerpt:
1.26.2 of the Microsoft PyPI package agent-framework
- SCA from the excerpt:
101 npm security advisories
GHSA-8x4p-wc99-jvgr: Malware in @nullzero/urlcat
@nullzero/urlcat >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8x4p-wc99-jvgr: Malware
- SCA from the title:
GHSA-64x2-qm25-qchx: Malware in themecolors-debug-renderloop
themecolors-debug-renderloop >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-64x2-qm25-qchx: Malware
- SCA from the title:
GHSA-gv36-5pf2-g6mm: Malware in transitions-promise-segmentedcontrol
transitions-promise-segmentedcontrol >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gv36-5pf2-g6mm: Malware
- SCA from the title:
GHSA-3rv4-9xw7-647g: Malware in universallinks-unit
universallinks-unit >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3rv4-9xw7-647g: Malware
- SCA from the title:
GHSA-5ccv-4rc8-vhxj: Malware in fallback-datepicker-fcm
fallback-datepicker-fcm >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5ccv-4rc8-vhxj: Malware
- SCA from the title:
GHSA-cxwc-2pvw-6q7w: Malware in json-asyncapi
json-asyncapi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cxwc-2pvw-6q7w: Malware
- SCA from the title:
GHSA-965x-hqvq-32wm: Malware in barcodescanner-network-webgl
barcodescanner-network-webgl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-965x-hqvq-32wm: Malware
- SCA from the title:
GHSA-v8v5-9cm7-w7fx: Malware in fcm-gps-database
fcm-gps-database >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v8v5-9cm7-w7fx: Malware
- SCA from the title:
GHSA-m4c5-mjh5-qjx9: Malware in listviews-actionbars
listviews-actionbars >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m4c5-mjh5-qjx9: Malware
- SCA from the title:
GHSA-qfmf-qvcv-mmvj: Malware in lazyloading-haptics
lazyloading-haptics >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-qfmf-qvcv-mmvj: Malware
- SCA from the title:
GHSA-cf5m-mcj9-vqc4: Malware in font-picker-responsive
font-picker-responsive >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cf5m-mcj9-vqc4: Malware
- SCA from the title:
GHSA-cwpf-wq82-v7rx: Malware in buildautomation-touch
buildautomation-touch >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cwpf-wq82-v7rx: Malware
- SCA from the title:
GHSA-wmfg-5hm7-5fqc: Malware in request-tracking-sqlite
request-tracking-sqlite >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wmfg-5hm7-5fqc: Malware
- SCA from the title:
GHSA-rj26-7q2x-2725: Malware in svg-photos
svg-photos >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rj26-7q2x-2725: Malware
- SCA from the title:
GHSA-7qx6-87jx-fv76: Malware in continuousintegration-cicd-compression
continuousintegration-cicd-compression >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7qx6-87jx-fv76: Malware
- SCA from the title:
GHSA-vvxq-vgwc-w868: Malware in imagegalleries-homescreen
imagegalleries-homescreen >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vvxq-vgwc-w868: Malware
- SCA from the title:
GHSA-hwmh-mj35-gf8m: Malware in macos-contentprovider-optimizingassets
macos-contentprovider-optimizingassets >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hwmh-mj35-gf8m: Malware
- SCA from the title:
GHSA-7mwg-cm3x-mhf2: Malware in interaction-photos-infinitescroll
interaction-photos-infinitescroll >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7mwg-cm3x-mhf2: Malware
- SCA from the title:
GHSA-3cpm-73mm-8v5w: Malware in designsystem-vector
designsystem-vector >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3cpm-73mm-8v5w: Malware
- SCA from the title:
GHSA-58hm-vpp8-gfq5: Malware in framerate-interaction-permissions
framerate-interaction-permissions >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-58hm-vpp8-gfq5: Malware
- SCA from the title:
GHSA-v95h-r5rw-hwm9: Malware in touchid-images
touchid-images >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v95h-r5rw-hwm9: Malware
- SCA from the title:
GHSA-94v5-g84v-4fph: Malware in documents-widgets
documents-widgets >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-94v5-g84v-4fph: Malware
- SCA from the title:
GHSA-4q39-f3fm-23jf: Malware in analytics-readability-gestures
analytics-readability-gestures >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4q39-f3fm-23jf: Malware
- SCA from the title:
GHSA-8qcx-vgc7-fxj7: Malware in virtualization-compression-collapse
virtualization-compression-collapse >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8qcx-vgc7-fxj7: Malware
- SCA from the title:
GHSA-pqp6-f44c-7fxp: Malware in pushnotifications-gesturerecognition
pushnotifications-gesturerecognition >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pqp6-f44c-7fxp: Malware
- SCA from the title:
GHSA-7vw4-cwm8-6v4j: Malware in onesignal-hooks
onesignal-hooks >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7vw4-cwm8-6v4j: Malware
- SCA from the title:
GHSA-cg52-25pp-83hw: Malware in datapersistence-profiling
datapersistence-profiling >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cg52-25pp-83hw: Malware
- SCA from the title:
GHSA-gcwg-gvrj-42wv: Malware in actionbars-infinitescroll-searchbar
actionbars-infinitescroll-searchbar >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gcwg-gvrj-42wv: Malware
- SCA from the title:
GHSA-jfv5-732c-9w38: Malware in flexbox-oauth-machinelearning
flexbox-oauth-machinelearning >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jfv5-732c-9w38: Malware
- SCA from the title:
GHSA-jwhm-7xjm-8qg7: Malware in react-native-game-utils
react-native-game-utils >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jwhm-7xjm-8qg7: Malware
- SCA from the title:
GHSA-x2vm-cf3p-m2w8 / CVE-2026-119793: libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config
@libp2p/gossipsub < 17.0.0 → 17.0.0
Why tagged?
- SCA from the title:
GHSA-x2vm-cf3p-m2w8 / CVE-202
- SCA from the title:
GHSA-rvfr-cqwq-rc4j / CVE-2026-110789: libp2p: ASN.1 DER decoder drives an unbounded synchronous loop on attacker-controlled length fields, stalling the Node event loop pre-auth
@libp2p/crypto <= 5.1.21 → 5.1.22
Why tagged?
- SCA from the title:
GHSA-rvfr-cqwq-rc4j / CVE-202
- SCA from the title:
GHSA-3x95-6m73-ggv2: Malware in cookie-parser-ease
cookie-parser-ease >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3x95-6m73-ggv2: Malware
- SCA from the title:
GHSA-ff57-xr4p-6v9g: Malware in leobot-cli
leobot-cli >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-ff57-xr4p-6v9g: Malware
- SCA from the title:
GHSA-gvx2-mxgq-hwmp: Malware in warpcast
warpcast >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gvx2-mxgq-hwmp: Malware
- SCA from the title:
GHSA-rxxq-8r5h-h659: Malware in warpcast-bot
warpcast-bot >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rxxq-8r5h-h659: Malware
- SCA from the title:
GHSA-5mh8-33rf-fvgp: Malware in kartykgithub-bulk-multi
kartykgithub-bulk-multi = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-5mh8-33rf-fvgp: Malware
- SCA from the title:
GHSA-62rq-mxgx-jvm9: Malware in kartykgithub-bulk-versions
kartykgithub-bulk-versions = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-62rq-mxgx-jvm9: Malware
- SCA from the title:
GHSA-89cp-3m64-fh5x: Malware in rea1ity-tool
rea1ity-tool >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-89cp-3m64-fh5x: Malware
- SCA from the title:
GHSA-q543-mmv3-jp95: Malware in afreumtoolkits
afreumtoolkits >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q543-mmv3-jp95: Malware
- SCA from the title:
GHSA-q3w6-mmxq-2c3f: Malware in tscscan
tscscan >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q3w6-mmxq-2c3f: Malware
- SCA from the title:
GHSA-h3wg-5whf-3q6m: Malware in @suruj/tsc-p2p
@suruj/tsc-p2p >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h3wg-5whf-3q6m: Malware
- SCA from the title:
GHSA-687q-whjx-h5r5: Malware in tsc-ai
tsc-ai >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-687q-whjx-h5r5: Malware
- SCA from the title:
GHSA-8ffh-66gm-68xr: Malware in tsc-mesh
tsc-mesh >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8ffh-66gm-68xr: Malware
- SCA from the title:
GHSA-4q8v-g74j-hp8x: Malware in tsc-polymorph
tsc-polymorph >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4q8v-g74j-hp8x: Malware
- SCA from the title:
GHSA-63cp-73jc-263x: Malware in tsc-lotl
tsc-lotl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-63cp-73jc-263x: Malware
- SCA from the title:
GHSA-mr52-vq6q-4j64: Malware in @suruj/scan-dog
@suruj/scan-dog >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mr52-vq6q-4j64: Malware
- SCA from the title:
GHSA-cqw3-7xmc-xf28: Malware in tsc-p2pnet
tsc-p2pnet >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cqw3-7xmc-xf28: Malware
- SCA from the title:
GHSA-vwh3-h34w-8h34: Malware in tsc-wireshift
tsc-wireshift >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vwh3-h34w-8h34: Malware
- SCA from the title:
GHSA-pc2h-6mph-p3r3: Malware in zk-scandog
zk-scandog >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pc2h-6mph-p3r3: Malware
- SCA from the title:
GHSA-cq6v-27f7-grj2: Malware in edulabs
edulabs >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cq6v-27f7-grj2: Malware
- SCA from the title:
GHSA-w67p-3hvj-8rq9: Malware in whs4_eud
whs4_eud >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w67p-3hvj-8rq9: Malware
- SCA from the title:
GHSA-764r-557p-9hgx: Malware in wallet-modal-223
wallet-modal-223 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-764r-557p-9hgx: Malware
- SCA from the title:
GHSA-38qc-cchj-49wq: Malware in sw-pluginer
sw-pluginer >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-38qc-cchj-49wq: Malware
- SCA from the title:
GHSA-3r65-5c5p-4pq5: Malware in tailwindcss-animatemotion
tailwindcss-animatemotion >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3r65-5c5p-4pq5: Malware
- SCA from the title:
GHSA-5rm2-63mr-98hm: Malware in tailwindcss-motionanimate
tailwindcss-motionanimate >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5rm2-63mr-98hm: Malware
- SCA from the title:
GHSA-8x7q-hxcj-jghm: Malware in framer-motionanimate
framer-motionanimate >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8x7q-hxcj-jghm: Malware
- SCA from the title:
GHSA-6jv6-hpqq-w5pr: Malware in @doublekk61_pro/postcss-motion-animation
@doublekk61_pro/postcss-motion-animation >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6jv6-hpqq-w5pr: Malware
- SCA from the title:
GHSA-6545-fg56-534w: Malware in rel-zone
rel-zone = 9.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-6545-fg56-534w: Malware
- SCA from the title:
GHSA-cvvv-42qm-w4qp: Malware in flexible-layout-tools
flexible-layout-tools >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cvvv-42qm-w4qp: Malware
- SCA from the title:
GHSA-6jwf-qr9f-vxp2: Malware in @utilityforge/dynamic-interface-kit
@utilityforge/dynamic-interface-kit >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6jwf-qr9f-vxp2: Malware
- SCA from the title:
GHSA-63r3-2637-f8jf: Malicious code in singpass-myinfo-oidc-helper (npm)
singpass-myinfo-oidc-helper = 0.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-63r3-2637-f8jf: Maliciou
- SCA from the title:
GHSA-q37r-5xxr-6v4x: Malware in vamp-mcp
vamp-mcp = 0.2.4 → remove it | = 0.2.5 → remove it
Why tagged?
- SCA from the title:
GHSA-q37r-5xxr-6v4x: Malware
- AI Security from the title:
GHSA-q37r-5xxr-6v4x: Malware in vamp-mcp
- SCA from the title:
GHSA-pv6m-32xh-4r4w: Malware in jaysift
jaysift = 1.5.0 → remove it
Why tagged?
- SCA from the title:
GHSA-pv6m-32xh-4r4w: Malware
- SCA from the title:
GHSA-qx2j-6rj5-6mqx: Malicious code in base64-x58 (npm)
base64-x58 > 0 → remove it | = 0.0.1 → remove it | = 0.0.5 → remove it
Why tagged?
- SCA from the title:
GHSA-qx2j-6rj5-6mqx: Maliciou
- SCA from the title:
GHSA-mh48-jfmg-8gjv: Malicious code in ethers-wallet-latest (npm)
ethers-wallet-latest = 5.8.0 → remove it
Why tagged?
- SCA from the title:
GHSA-mh48-jfmg-8gjv: Maliciou
- SCA from the title:
GHSA-vcm3-3h6p-h62v: Malicious code in @brandkit/theme (npm)
@brandkit/theme = 2.4.1 → remove it | = 2.4.2 → remove it
Why tagged?
- SCA from the title:
GHSA-vcm3-3h6p-h62v: Maliciou
- SCA from the title:
GHSA-c9cq-9rpq-6v74: Malicious code in mexc-utils-helper (npm)
mexc-utils-helper = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-c9cq-9rpq-6v74: Maliciou
- SCA from the title:
GHSA-46wp-p4c2-3637: Malicious code in on-direct-click (npm)
on-direct-click = 99.9.0 → remove it
Why tagged?
- SCA from the title:
GHSA-46wp-p4c2-3637: Maliciou
- SCA from the title:
GHSA-wvvr-fpw5-74ph: Malicious code in ui-universal-auth (npm)
ui-universal-auth = 99.9.0 → remove it
Why tagged?
- SCA from the title:
GHSA-wvvr-fpw5-74ph: Maliciou
- SCA from the title:
GHSA-85g5-ghvw-f2p2: Malicious code in bs58-60 (npm)
bs58-60 = 6.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-85g5-ghvw-f2p2: Maliciou
- SCA from the title:
GHSA-v87g-929x-2rg9: Malicious code in serverless-env-helpers (npm)
serverless-env-helpers = 1.0.0 → remove it | = 1.0.1 → remove it | = 1.0.2 → remove it | = 1.0.3 → remove it | = 1.0.4 → remove it | = 1.0.5 → remove it; +2 more
Why tagged?
- SCA from the title:
GHSA-v87g-929x-2rg9: Maliciou
- SCA from the title:
GHSA-5qxj-6f2x-27qm: Malicious code in serverless-env-utils (npm)
serverless-env-utils = 1.0.0 → remove it | = 1.0.2 → remove it | = 1.0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-5qxj-6f2x-27qm: Maliciou
- SCA from the title:
GHSA-7rmh-jh38-g275: Malicious code in base128-x58 (npm)
base128-x58 > 0 → remove it | = 0.0.1 → remove it | = 0.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-7rmh-jh38-g275: Maliciou
- SCA from the title:
GHSA-qwx4-3p78-j896: Malicious code in node-bs58.js (npm)
node-bs58.js > 0 → remove it | = 1.0.0 → remove it | = 3.0.0 → remove it | = 4.0.0 → remove it | = 4.0.1 → remove it | = 4.0.2 → remove it; +5 more
Why tagged?
- SCA from the title:
GHSA-qwx4-3p78-j896: Maliciou
- SCA from the title:
GHSA-rj96-rg6c-9hw8: Malicious code in @wppconnect-team/wppconnect (npm)
@wppconnect-team/wppconnect = 2.4.1 → remove it
Why tagged?
- SCA from the title:
GHSA-rj96-rg6c-9hw8: Maliciou
- SCA from the title:
GHSA-c2r9-jmw4-552r: Malicious code in approve-audit (npm)
approve-audit = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-c2r9-jmw4-552r: Maliciou
- SCA from the title:
GHSA-pr75-5v46-hgrg: Malicious code in base60-58x (npm)
base60-58x > 0 → remove it | = 5.0.2 → remove it | = 5.0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-pr75-5v46-hgrg: Maliciou
- SCA from the title:
GHSA-fg94-4m25-m7g2: Malicious code in npm-bs58.js (npm)
npm-bs58.js > 0 → remove it | = 1.0.0 → remove it | = 2.0.1 → remove it | = 2.0.2 → remove it | = 6.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-fg94-4m25-m7g2: Maliciou
- SCA from the title:
GHSA-96hm-h5v4-92fq: Malicious code in @wppconnect/server (npm)
@wppconnect/server = 2.10.82 → remove it
Why tagged?
- SCA from the title:
GHSA-96hm-h5v4-92fq: Maliciou
- SCA from the title:
GHSA-r87g-8hwq-8mxh: Malicious code in signup-lib (npm)
signup-lib = 99.99.99 → remove it
Why tagged?
- SCA from the title:
GHSA-r87g-8hwq-8mxh: Maliciou
- SCA from the title:
GHSA-6q7h-xj7v-46gr: Malicious code in csci-internal (npm)
csci-internal = 99.1.1 → remove it
Why tagged?
- SCA from the title:
GHSA-6q7h-xj7v-46gr: Maliciou
- SCA from the title:
GHSA-4p4q-f2g8-m99p: Malicious code in me5123 (npm)
me5123 = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-4p4q-f2g8-m99p: Maliciou
- SCA from the title:
GHSA-878x-ph8x-7cx2: Malicious code in @public-for-cdao/providers (npm)
@public-for-cdao/providers = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-878x-ph8x-7cx2: Maliciou
- SCA from the title:
GHSA-g32j-5xrq-mg65: Malicious code in lgcook (npm)
lgcook = 99.1.1 → remove it
Why tagged?
- SCA from the title:
GHSA-g32j-5xrq-mg65: Maliciou
- SCA from the title:
GHSA-4p56-w4hr-hjgq: Malware in sendy-kaitoz11
sendy-kaitoz11 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4p56-w4hr-hjgq: Malware
- SCA from the title:
GHSA-wq4w-c9cq-7qj5: Malware in @finxsecdemo/utils
@finxsecdemo/utils >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wq4w-c9cq-7qj5: Malware
- SCA from the title:
GHSA-vm9x-v62c-4c5w: Malware in jito-bundle-tip-service
jito-bundle-tip-service >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vm9x-v62c-4c5w: Malware
- SCA from the title:
GHSA-mx6m-c89f-wfwj: Malware in jito-bundle-service
jito-bundle-service >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mx6m-c89f-wfwj: Malware
- SCA from the title:
GHSA-6r5j-jqgh-fx86: Malware in jito-bundle-tip
jito-bundle-tip >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6r5j-jqgh-fx86: Malware
- SCA from the title:
GHSA-wh7w-5cfq-qpqx: Malware in jito-bundle
jito-bundle >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wh7w-5cfq-qpqx: Malware
- SCA from the title:
GHSA-vm4g-cpqx-24px: Malware in @ifasn/mmdd-doc-mcp
@ifasn/mmdd-doc-mcp >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vm4g-cpqx-24px: Malware
- AI Security from the title:
GHSA-vm4g-cpqx-24px: Malware in @ifasn/mmdd-doc-mcp
- SCA from the title:
GHSA-3f74-wcv7-jw8f: Malware in @ifasn/ms-doc-mcp
@ifasn/ms-doc-mcp >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3f74-wcv7-jw8f: Malware
- AI Security from the title:
GHSA-3f74-wcv7-jw8f: Malware in @ifasn/ms-doc-mcp
- SCA from the title:
GHSA-pph8-xw8c-ffc5: Malware in babyyodaa
babyyodaa >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pph8-xw8c-ffc5: Malware
- SCA from the title:
GHSA-rrvh-j339-43h2: Malware in gugodapis
gugodapis >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rrvh-j339-43h2: Malware
- SCA from the title:
GHSA-xpgg-qvpw-c4wp: Malware in gugodapistram
gugodapistram >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xpgg-qvpw-c4wp: Malware
- SCA from the title:
GHSA-3789-66mp-728c: Malware in gugoddiscordapi
gugoddiscordapi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3789-66mp-728c: Malware
- SCA from the title:
GHSA-fqxw-3hw8-qhcx: Malware in gogodstramapi
gogodstramapi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-fqxw-3hw8-qhcx: Malware
- SCA from the title:
GHSA-8jqw-fp72-48fv: Malware in apigugod
apigugod >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8jqw-fp72-48fv: Malware
- SCA from the title:
GHSA-c372-wcrj-xqv3: Malware in gugodapi
gugodapi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c372-wcrj-xqv3: Malware
- SCA from the title:
GHSA-4q9g-pqm4-x4v7: Malware in gogodapiapp
gogodapiapp >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4q9g-pqm4-x4v7: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
Cloud keys leaked in Docker Hub images are stolen within seconds
Credentials and access secrets exposed in public Docker Hub images are being extracted and exploited by attackers within as little as eight seconds of publication. [...]
Why tagged?
- SCA from the excerpt:
crets exposed in public Docker Hub images are being extrac
- SCA from the excerpt:
4 Packagist security advisories
GHSA-r7hw-jx6r-756g / CVE-2026-110782: SAML2: Incomplete fix of CVE-2026-49283: unsigned embedded Response bypasses HTTP-Artifact signature verification (no embedded-Issuer binding)
simplesamlphp/saml2 >= 6.2.2, <= 6.2.3 → 6.2.4 | >= 7.0.0-rc1, < 7.0.0-rc2 → 7.0.0-rc2
Why tagged?
- SCA from the title:
GHSA-r7hw-jx6r-756g / CVE-202
- SCA from the title:
GHSA-8vm9-f75m-5h2m / CVE-2026-69241: Filament Curator: Stored XSS via unsanitized SVG upload served inline
awcodes/filament-curator >= 5.0.0, <= 5.1.1 → 5.1.2 | >= 4.0.0, <= 4.1.1 → 4.1.2 | >= 3.0.0, <= 3.7.8 → 3.7.9
Why tagged?
- SCA from the title:
GHSA-8vm9-f75m-5h2m / CVE-202
- SCA from the title:
GHSA-828w-6qgx-3rcf / CVE-2026-63389: Filament Curator: Cross-tenant media metadata disclosure via Curator picker search
awcodes/filament-curator >= 5.0.0, < 5.1.1 → 5.1.1 | >= 4.0.0, < 4.1.1 → 4.1.1 | >= 3.2.4, < 3.7.8 → 3.7.8
Why tagged?
- SCA from the title:
GHSA-828w-6qgx-3rcf / CVE-202
- SCA from the title:
GHSA-pr4x-6fj4-gm4h / CVE-2026-63672: EGroupware: User-Controlled Identity Provider Selection in SAML Authentication
egroupware/egroupware < 23.1.20260601 → 23.1.20260601 | >= 26.0.20251208, < 26.6.20260616 → 26.6.20260616
Why tagged?
- SCA from the title:
GHSA-pr4x-6fj4-gm4h / CVE-202
- SCA from the title:
All Packagist advisories · each advisory is independent, not one campaign
1 Go security advisory
GHSA-xhv5-8fpq-g7hf / CVE-2026-62336: qbee-agent: Local Privilege Escalation and Arbitrary File Tampering via Symlink Following in createFile helper
go.qbee.io/agent < 0.0.0-20260615134032-0fdf8e411de5 → 0.0.0-20260615134032-0fdf8e411de5
Why tagged?
- SCA from the title:
GHSA-xhv5-8fpq-g7hf / CVE-202
- SCA from the title:
All Go advisories · each advisory is independent, not one campaign
Borrowed Code, Real Consequences: What OPTIMJACK Teaches Us
The OPTIMJACK supply chain attack demonstrates how a compromised vendor script can expose websites, highlighting the need for strict segmentation.
Why tagged?
- SCA from the excerpt:
The OPTIMJACK supply chain attack demonstrates how a comp
- SCA from the excerpt:
1 Maven security advisory
GHSA-c5q4-97jw-jggh / CVE-2026-14265: AWS-advanced-jdbc-wrapper: Java Deserialization RCE via Cache Poisoning
software.amazon.jdbc:aws-advanced-jdbc-wrapper >= 3.3.0, < 4.0.1 → 4.0.1
Why tagged?
- SCA from the title:
GHSA-c5q4-97jw-jggh / CVE-202
- SCA from the title:
All Maven advisories · each advisory is independent, not one campaign
7 PyPI security advisories
GHSA-v858-xh7w-8jr5 / CVE-2026-63634: pympp allows excessive sponsored transaction fees through padded calldata
pympp < 0.9.1 → 0.9.1
Why tagged?
- SCA from the title:
GHSA-v858-xh7w-8jr5 / CVE-202
- SCA from the title:
GHSA-gfv3-m769-5xm3 / CVE-2026-53998: Phoenix: Format String Injection in applyChatTemplate
arize-phoenix >= 13.0.0, < 15.7.0 → 15.7.0
Why tagged?
- SCA from the title:
GHSA-gfv3-m769-5xm3 / CVE-202
- SCA from the title:
GHSA-g97f-vppp-p428: Malicious code in mcp-aevo-server (PyPI)
mcp-aevo-server = 0.2.0 → remove it | = 0.2.0.post1 → remove it | = 0.2.0.post2 → remove it | = 0.2.0.post3 → remove it | = 0.2.0.post4 → remove it | = 0.2.0.post6 → remove it
Why tagged?
- SCA from the title:
GHSA-g97f-vppp-p428: Maliciou
- AI Security from the title:
GHSA-g97f-vppp-p428: Malicious code in mcp-aevo-server (PyPI)
- SCA from the title:
GHSA-4c84-hmpx-q5wj: Malicious code in pepestyglo (PyPI)
pepestyglo = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-4c84-hmpx-q5wj: Maliciou
- SCA from the title:
GHSA-q7f6-x6q9-25jm: Malicious code in lampouali (PyPI)
lampouali = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-q7f6-x6q9-25jm: Maliciou
- SCA from the title:
GHSA-6rr6-px42-fhx3: Malicious code in logger-prefix-buffer-lexer (PyPI)
logger-prefix-buffer-lexer = 1.0.0 → remove it | = 1.0.0.post1 → remove it
Why tagged?
- SCA from the title:
GHSA-6rr6-px42-fhx3: Maliciou
- SCA from the title:
GHSA-v9m2-f332-4x3q: Malicious code in pliktre (PyPI)
pliktre = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-v9m2-f332-4x3q: Maliciou
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
Clearer Security Signals: Making Attestations Comprehensible for PyPI Users
To help developers and package consumers better understand software supply-chain security, the OpenSSF Securing Software Repositories Working Group created an Attestations Style Guide—and its recommendations are now live on PyPI with redesigned project pages and a dedicated…
Why tagged?
- SCA from the excerpt:
When package registries such as PyPI, RubyGems,
- SCA from the excerpt:
OPTIMJACK: When Trusted JavaScript Becomes a Supply Chain Attack
How a vulnerability in Optimizely exposed visitors of at least 178 organizations’ websites to malicious code, revealing a critical blind spot in third-party software trust.
Why tagged?
- SCA from the title:
ed JavaScript Becomes a Supply Chain Attack
- SCA from the title:
GHSA-vc7v-qv4w-wrv8 / CVE-2026-119351: Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
next >= 16.2.0, <= 16.4.4 → 16.4.5
Why tagged?
- SCA from the title:
GHSA-vc7v-qv4w-wrv8 / CVE-202
- SCA from the title:
2 RubyGems security advisories
GHSA-2v7g-f6xp-g45h: Malicious code in node-test-repo (RubyGems)
node-test-repo = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-2v7g-f6xp-g45h: Maliciou
- SCA from the title:
GHSA-wv87-wqgm-mf6r: Malicious code in solana-keypair (RubyGems)
solana-keypair = 0.1.0 → remove it
Why tagged?
- SCA from the title:
GHSA-wv87-wqgm-mf6r: Maliciou
- SCA from the title:
All RubyGems advisories · each advisory is independent, not one campaign
Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap
Pinning GitHub Actions to an exact version of their code, known as SHA pinning, has become the go-to defense against software supply chain attacks. Attackers have already found a way around it. In March 2026, the hackers who hijacked Trivy, a widely used open-source security…
Why tagged?
- SCA from the excerpt:
Pinning GitHub Actions to an exact version of
- SCA from the excerpt:
Optimizely supply chain attack served malware on CNN, Fox News, BBC sites
A suspected supply chain attack targeting Optimizely has led to malicious JavaScript being loaded on numerous popular websites, including Zoom, CNN, Fox News, BBC, Salesforce, and GitLab, exposing visitors to scripts designed to steal cryptocurrency and payment information and…
Why tagged?
- SCA from the title:
Optimizely supply chain attack served malware on CNN,
- SCA from the title:
WPPConnect Compromised: Malicious Releases Steal Secrets and WhatsApp Sessions Through the Project's Own Pipeline
Malicious WPPConnect npm releases 2.4.1 and 2.10.82 steal secrets and WhatsApp sessions via Telegram. Affected versions, how they shipped and what to rotate.
Why tagged?
- SCA from the excerpt:
Malicious WPPConnect npm releases 2.4.1 and 2.10
- SCA from the excerpt:
116 npm security advisories
GHSA-57c9-vqf7-cxmv: Malware in quickwinston
quickwinston >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-57c9-vqf7-cxmv: Malware
- SCA from the title:
GHSA-f94p-qwjw-q564: Malware in @jisan901/teamfocus
@jisan901/teamfocus >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f94p-qwjw-q564: Malware
- SCA from the title:
GHSA-r747-fv5r-923c: Malware in @jisan901/fs-browser
@jisan901/fs-browser >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-r747-fv5r-923c: Malware
- SCA from the title:
GHSA-wjf6-c53r-6x9h: Malware in kartykgithub-bulk-rollback
kartykgithub-bulk-rollback = 0.0.0-stage → remove it | = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-wjf6-c53r-6x9h: Malware
- SCA from the title:
GHSA-7h45-q5jx-7r87 / CVE-2026-129239: Directus: Share update allows reassigning user_created and role
directus < 12.3.1 → 12.3.1
Why tagged?
- SCA from the title:
GHSA-7h45-q5jx-7r87 / CVE-202
- SCA from the title:
GHSA-jq3q-62jc-fqq9 / CVE-2026-68934: code-review-mcp-server: Command injection via unsanitized folderPath/baseBranch parameters
code-review-mcp-server < 1.5.3 → 1.5.3
Why tagged?
- SCA from the title:
GHSA-jq3q-62jc-fqq9 / CVE-202
- AI Security from the title:
2026-68934: code-review-mcp-server: Command injection via unsanitized fold
- SCA from the title:
GHSA-r69m-249c-rm86: Malware in kartyk-test-unscoped-pkg
kartyk-test-unscoped-pkg = 0.0.0-stage → remove it | = 0.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-r69m-249c-rm86: Malware
- SCA from the title:
GHSA-22xg-369p-hqrf: Malware in kartykgithub-ph-d
kartykgithub-ph-d = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-22xg-369p-hqrf: Malware
- SCA from the title:
GHSA-jhjw-5w2x-mmh6: Malware in kartykgithub-ph-c
kartykgithub-ph-c = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-jhjw-5w2x-mmh6: Malware
- SCA from the title:
GHSA-q5wh-5wp7-j3cx: Malware in vite-vue-path-map
vite-vue-path-map >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q5wh-5wp7-j3cx: Malware
- SCA from the title:
GHSA-rrwf-2g66-3mp2: Malware in vite-auto-import-svg
vite-auto-import-svg >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rrwf-2g66-3mp2: Malware
- SCA from the title:
GHSA-8q65-mhm6-m4g3: Malware in vite-utils-svg-icon
vite-utils-svg-icon >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8q65-mhm6-m4g3: Malware
- SCA from the title:
GHSA-37hh-cmfp-pf7g: Malware in @shadowdu/memos-mcp
@shadowdu/memos-mcp >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-37hh-cmfp-pf7g: Malware
- AI Security from the title:
GHSA-37hh-cmfp-pf7g: Malware in @shadowdu/memos-mcp
- SCA from the title:
GHSA-56mh-v6h4-jx2f: Malware in @shadowdqj/image-mcp
@shadowdqj/image-mcp >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-56mh-v6h4-jx2f: Malware
- AI Security from the title:
GHSA-56mh-v6h4-jx2f: Malware in @shadowdqj/image-mcp
- SCA from the title:
GHSA-9hvg-j8mj-55xr: Malware in mem0-mcp-server
mem0-mcp-server >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9hvg-j8mj-55xr: Malware
- AI Security from the title:
GHSA-9hvg-j8mj-55xr: Malware in mem0-mcp-server
- SCA from the title:
GHSA-92hx-vmg8-hp5j: Malware in lodash-base-unary
lodash-base-unary >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-92hx-vmg8-hp5j: Malware
- SCA from the title:
GHSA-v68r-r4xh-39qw: Malware in moidevl
moidevl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-v68r-r4xh-39qw: Malware
- SCA from the title:
GHSA-4vr9-jfrh-4qrp: Malware in wasm-jzwl981
wasm-jzwl981 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4vr9-jfrh-4qrp: Malware
- SCA from the title:
GHSA-gvw5-v3wj-mw25: Malware in @devforgespr/postcss-animation-toolkit
@devforgespr/postcss-animation-toolkit >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gvw5-v3wj-mw25: Malware
- SCA from the title:
GHSA-r5j2-g4j2-hvmg: Malware in tailwindcss-pixel-tools
tailwindcss-pixel-tools >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-r5j2-g4j2-hvmg: Malware
- SCA from the title:
GHSA-3v6f-vw6p-23x8: Malware in ishumdz-bail
ishumdz-bail >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3v6f-vw6p-23x8: Malware
- SCA from the title:
GHSA-gqpv-qm3x-6j29: Malware in kerl-kpi
kerl-kpi >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gqpv-qm3x-6j29: Malware
- SCA from the title:
GHSA-mcf9-m992-w7q6: Malware in iguro-ytdl
iguro-ytdl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mcf9-m992-w7q6: Malware
- SCA from the title:
GHSA-cfm7-5mcw-875g: Malware in obanai-apis
obanai-apis >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cfm7-5mcw-875g: Malware
- SCA from the title:
GHSA-j7f7-r56m-fxp5: Malware in wailib
wailib >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j7f7-r56m-fxp5: Malware
- SCA from the title:
GHSA-9rjx-j23v-pmwg: Malware in @finzzcloud/baileys
@finzzcloud/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9rjx-j23v-pmwg: Malware
- SCA from the title:
GHSA-mm36-x4rc-79r6: Malware in @yoshinos1/npm-shell
@yoshinos1/npm-shell >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mm36-x4rc-79r6: Malware
- SCA from the title:
GHSA-5jg8-2567-v8gh: Malware in @risacakep/risayap
@risacakep/risayap >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5jg8-2567-v8gh: Malware
- SCA from the title:
GHSA-8xjg-cj37-5g9g: Malware in astia-alabki-malosskiafa
astia-alabki-malosskiafa = 1.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-8xjg-cj37-5g9g: Malware
- SCA from the title:
GHSA-63h3-h23c-q4c7: Malware in astam-ifut-dakiula
astam-ifut-dakiula = 1.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-63h3-h23c-q4c7: Malware
- SCA from the title:
GHSA-mwcf-xxwp-hqg7: Malware in astam-ifst-diakavgya
astam-ifst-diakavgya = 1.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-mwcf-xxwp-hqg7: Malware
- SCA from the title:
GHSA-ggrv-xjj2-x53j: Malware in astam-ifst-diakav
astam-ifst-diakav = 1.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-ggrv-xjj2-x53j: Malware
- SCA from the title:
GHSA-9pvx-7hc7-qc6h: Malware in @lymmhere/lymmexc
@lymmhere/lymmexc >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9pvx-7hc7-qc6h: Malware
- SCA from the title:
GHSA-x3q5-98g2-2vg5: Malware in astam-ifst-dia
astam-ifst-dia = 1.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-x3q5-98g2-2vg5: Malware
- SCA from the title:
GHSA-7qrf-v9pj-7cwh: Malware in augis-pomoi9r-nc
augis-pomoi9r-nc = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-7qrf-v9pj-7cwh: Malware
- SCA from the title:
GHSA-9wfg-j6pq-3c8f: Malware in supunmd-bail
supunmd-bail >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-9wfg-j6pq-3c8f: Malware
- SCA from the title:
GHSA-4fvr-hmr9-rm3h: Malware in ai-apis
ai-apis >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4fvr-hmr9-rm3h: Malware
- SCA from the title:
GHSA-c623-3fx8-8xcg: Malware in @mr-supun-fernando/news-scrap
@mr-supun-fernando/news-scrap >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c623-3fx8-8xcg: Malware
- SCA from the title:
GHSA-wqv4-64mh-f93c: Malware in @mr-supun-fernando/supunmd-bail
@mr-supun-fernando/supunmd-bail >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wqv4-64mh-f93c: Malware
- SCA from the title:
GHSA-m4wc-wx5j-qw6w: Malware in supun-baileyz
supun-baileyz >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m4wc-wx5j-qw6w: Malware
- SCA from the title:
GHSA-27ch-2mmj-q5wx: Malware in augis-pomo9r-nusfida
augis-pomo9r-nusfida = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-27ch-2mmj-q5wx: Malware
- SCA from the title:
GHSA-39pc-r8f9-6m59: Malware in augis-pomdoi9r-nutisafi
augis-pomdoi9r-nutisafi = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-39pc-r8f9-6m59: Malware
- SCA from the title:
GHSA-gpm5-494f-6gpq: Malware in internallib_v79
internallib_v79 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gpm5-494f-6gpq: Malware
- SCA from the title:
GHSA-6r46-rjqg-r8p8: Malware in augis-pod9r-nutyas
augis-pod9r-nutyas = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-6r46-rjqg-r8p8: Malware
- SCA from the title:
GHSA-g883-gm2g-xchg: Malware in augis-po9r-munafpipoa
augis-po9r-munafpipoa = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-g883-gm2g-xchg: Malware
- SCA from the title:
GHSA-89x5-qjj6-45mv: Malware in augis-lepaod-matiparahia
augis-lepaod-matiparahia = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-89x5-qjj6-45mv: Malware
- SCA from the title:
GHSA-269c-w973-vjw6: Malware in @mimecast-ui/directory-sync
@mimecast-ui/directory-sync >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-269c-w973-vjw6: Malware
- SCA from the title:
GHSA-xq37-6wr5-vfp8: Malware in mimecast-web-components
mimecast-web-components >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xq37-6wr5-vfp8: Malware
- SCA from the title:
GHSA-4qgp-3687-j3v3: Malware in @mimecast-ui/table-store
@mimecast-ui/table-store >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4qgp-3687-j3v3: Malware
- SCA from the title:
GHSA-hpc7-9758-p4fq: Malware in @mimecast-ui/charts
@mimecast-ui/charts >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hpc7-9758-p4fq: Malware
- SCA from the title:
GHSA-hw2m-wxqw-r2xg: Malware in @mimecast-ui/components
@mimecast-ui/components >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hw2m-wxqw-r2xg: Malware
- SCA from the title:
GHSA-m9hx-57c4-w8m3: Malware in astia-alao-mafadi12paf
astia-alao-mafadi12paf = 1.2.2 → remove it
Why tagged?
- SCA from the title:
GHSA-m9hx-57c4-w8m3: Malware
- SCA from the title:
GHSA-hwvp-2633-86vg: Malware in @luckylillia/plugin-nt-protocol
@luckylillia/plugin-nt-protocol = 1.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-hwvp-2633-86vg: Malware
- SCA from the title:
GHSA-c2qr-82xm-x8m4: Malware in @ubedsockets/baileys
@ubedsockets/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c2qr-82xm-x8m4: Malware
- SCA from the title:
GHSA-7mj5-hw2f-gggp: Malware in @baileysmod-ubed/baileys
@baileysmod-ubed/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7mj5-hw2f-gggp: Malware
- SCA from the title:
GHSA-c644-r8pf-rm6g: Malware in @cygnus-finance/sdk
@cygnus-finance/sdk >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-c644-r8pf-rm6g: Malware
- SCA from the title:
GHSA-4457-ccp3-7jpx: Malware in @cygnusfi/sdk
@cygnusfi/sdk >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4457-ccp3-7jpx: Malware
- SCA from the title:
GHSA-xvg5-r28q-w3wm: Malware in @cygnus-dao/core
@cygnus-dao/core >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xvg5-r28q-w3wm: Malware
- SCA from the title:
GHSA-rf96-234g-wjf5: Malware in analytics-skd
analytics-skd >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rf96-234g-wjf5: Malware
- SCA from the title:
GHSA-h6rh-5vcm-85gr: Malware in upshift-sdk
upshift-sdk >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h6rh-5vcm-85gr: Malware
- SCA from the title:
GHSA-f452-j766-8jw6: Malware in cygnus-contract
cygnus-contract >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f452-j766-8jw6: Malware
- SCA from the title:
GHSA-fwcm-83xr-v7c9: Malware in @arks-labs/utils
@arks-labs/utils >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-fwcm-83xr-v7c9: Malware
- SCA from the title:
GHSA-jq2q-8r58-q95r: Malware in shadowmd-baileys
shadowmd-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jq2q-8r58-q95r: Malware
- SCA from the title:
GHSA-rp99-6r35-wmfv: Malware in shadowmd
shadowmd >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rp99-6r35-wmfv: Malware
- SCA from the title:
GHSA-xx8r-wq9m-xr4m: Malware in @shadowmd/libsignal-node
@shadowmd/libsignal-node >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-xx8r-wq9m-xr4m: Malware
- SCA from the title:
GHSA-gw9v-r2mq-fwgf: Malware in spencer-btns
spencer-btns >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gw9v-r2mq-fwgf: Malware
- SCA from the title:
GHSA-448p-gp86-49g8: Malware in spencer-baileys
spencer-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-448p-gp86-49g8: Malware
- SCA from the title:
GHSA-8868-q7gh-f9jf: Malware in @sakataa/baileys
@sakataa/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8868-q7gh-f9jf: Malware
- SCA from the title:
GHSA-m26x-gv96-83jc: Malware in events-runtime
events-runtime >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-m26x-gv96-83jc: Malware
- SCA from the title:
GHSA-x35w-4cqq-26wj: Malware in shadowx-baileys
shadowx-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-x35w-4cqq-26wj: Malware
- SCA from the title:
GHSA-3485-jcp3-4jh6: Malware in @kingsaurus/libsignal-node
@kingsaurus/libsignal-node >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3485-jcp3-4jh6: Malware
- SCA from the title:
GHSA-f3p7-frfh-7cw2: Malware in sauruspro-bail
sauruspro-bail >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-f3p7-frfh-7cw2: Malware
- SCA from the title:
GHSA-858q-wcvq-9xxm: Malware in saurustheking
saurustheking >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-858q-wcvq-9xxm: Malware
- SCA from the title:
GHSA-hv4x-8vcp-h343: Malware in writecanvas
writecanvas >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hv4x-8vcp-h343: Malware
- SCA from the title:
GHSA-2fj2-477q-4h3f: Malware in luoxy-baileys
luoxy-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-2fj2-477q-4h3f: Malware
- SCA from the title:
GHSA-79m3-w5r2-mxg9: Malware in sauruskyah-baileys
sauruskyah-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-79m3-w5r2-mxg9: Malware
- SCA from the title:
GHSA-wv69-wpw9-p4x7: Malware in @lendkzn/baileys
@lendkzn/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wv69-wpw9-p4x7: Malware
- SCA from the title:
GHSA-x79p-hxf4-x2gm: Malware in mikuhost-agent
mikuhost-agent >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-x79p-hxf4-x2gm: Malware
- SCA from the title:
GHSA-7rcp-6hf7-x97v: Malware in mikuhostt-baileys
mikuhostt-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-7rcp-6hf7-x97v: Malware
- SCA from the title:
GHSA-ch6r-564g-q96h: Malware in @charape/baileys
@charape/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-ch6r-564g-q96h: Malware
- SCA from the title:
GHSA-5jr8-43jg-5544: Malware in @nerxa/socketon
@nerxa/socketon >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-5jr8-43jg-5544: Malware
- SCA from the title:
GHSA-g227-qwxx-j7gv: Malware in wanzy
wanzy >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-g227-qwxx-j7gv: Malware
- SCA from the title:
GHSA-q4rg-r9c6-4483: Malware in konsistent-provider
konsistent-provider >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-q4rg-r9c6-4483: Malware
- SCA from the title:
GHSA-8f4v-5fv4-7mfg: Malware in cantarel
cantarel >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8f4v-5fv4-7mfg: Malware
- SCA from the title:
GHSA-hcjm-wqvp-j2jq: Malware in @zeppeliorg/yt-sdl
@zeppeliorg/yt-sdl >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hcjm-wqvp-j2jq: Malware
- SCA from the title:
GHSA-cvqm-3f7h-rx5c: Malware in xzcgram
xzcgram >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cvqm-3f7h-rx5c: Malware
- SCA from the title:
GHSA-4vj2-rg7w-445m: Malware in xzcbailz
xzcbailz >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4vj2-rg7w-445m: Malware
- SCA from the title:
GHSA-6968-c77q-mj7c: Malware in @zeppeliorg/wbails
@zeppeliorg/wbails >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6968-c77q-mj7c: Malware
- SCA from the title:
GHSA-gjgf-mgph-2r5p: Malware in @zeppeliorg/xzcbailz
@zeppeliorg/xzcbailz >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-gjgf-mgph-2r5p: Malware
- SCA from the title:
GHSA-wfqw-vmc4-vv5j: Malware in @xzvbailss/xz-protect
@xzvbailss/xz-protect >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wfqw-vmc4-vv5j: Malware
- SCA from the title:
GHSA-4hv9-79qp-g8gc: Malware in @xzvbailss/baileys
@xzvbailss/baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4hv9-79qp-g8gc: Malware
- SCA from the title:
GHSA-jggq-cwwj-m26g: Malware in @xzvbailss/xzgateway
@xzvbailss/xzgateway >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jggq-cwwj-m26g: Malware
- SCA from the title:
GHSA-qgfg-72jv-6qpm: Malware in xzvbailss
xzvbailss >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-qgfg-72jv-6qpm: Malware
- SCA from the title:
GHSA-j9c9-h6xx-7m52: Malware in danz-bails
danz-bails >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j9c9-h6xx-7m52: Malware
- SCA from the title:
GHSA-g6rm-vv8x-j4fc: Malware in tailwindcss-motion-toolkit
tailwindcss-motion-toolkit >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-g6rm-vv8x-j4fc: Malware
- SCA from the title:
GHSA-97m8-2ch6-hxxj: Malware in inline-array
inline-array >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-97m8-2ch6-hxxj: Malware
- SCA from the title:
GHSA-qhmg-8r8f-cggq: Malware in express-json-database
express-json-database >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-qhmg-8r8f-cggq: Malware
- SCA from the title:
GHSA-wh49-9g69-vh2m: Malware in testpackage83
testpackage83 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-wh49-9g69-vh2m: Malware
- SCA from the title:
GHSA-7727-99j6-9x2v: Malware in elaina-baileys
elaina-baileys = 0.0.0-stage → remove it | = 1.0.0 → remove it | = 1.0.1 → remove it | = 1.0.2 → remove it | = 1.0.3 → remove it
Why tagged?
- SCA from the title:
GHSA-7727-99j6-9x2v: Malware
- SCA from the title:
GHSA-hcpm-2jg4-52mc: Malware in gimaa-baileys
gimaa-baileys >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-hcpm-2jg4-52mc: Malware
- SCA from the title:
GHSA-hf59-9xwc-2g4p / CVE-2026-128076: Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
nuxt >= 4.4.6, < 4.6.4 → 4.6.4 | >= 3.21.6, < 4.0.0 → no fix; @nuxt/nitro-server >= 4.4.6, < 4.6.4 → 4.6.4 | >= 3.21.6, < 4.0.0 → no fix · partly fixed
Why tagged?
- SCA from the title:
GHSA-hf59-9xwc-2g4p / CVE-202
- SCA from the title:
GHSA-96x6-fvhx-49hg / CVE-2026-128075: Nuxt exposes the message and data of unhandled errors thrown during server rendering
nuxt >= 4.0.0, < 4.6.4 → 4.6.4 | >= 3.0.0, < 4.0.0 → no fix · partly fixed
Why tagged?
- SCA from the title:
GHSA-96x6-fvhx-49hg / CVE-202
- SCA from the title:
GHSA-r9jc-w898-3fv6 / CVE-2026-128074: Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
nuxt >= 4.6.0, < 4.6.4 → 4.6.4
Why tagged?
- SCA from the title:
GHSA-r9jc-w898-3fv6 / CVE-202
- SCA from the title:
GHSA-x2wv-5868-p7v2 / CVE-2026-128072: @nuxt/webpack-builder and @nuxt/rspack-builder dev server serves built source to DNS rebinding pages
@nuxt/webpack-builder >= 4.0.0, < 4.6.4 → 4.6.4 | >= 3.0.0, < 4.0.0 → no fix; @nuxt/rspack-builder >= 4.0.0, < 4.6.4 → 4.6.4 | >= 3.12.2, < 4.0.0 → no fix · partly fixed
Why tagged?
- SCA from the title:
GHSA-x2wv-5868-p7v2 / CVE-202
- SCA from the title:
GHSA-f3x9-2chm-73c8 / CVE-2026-128071: Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes
nuxt >= 4.0.0, < 4.6.4 → 4.6.4 | >= 3.0.0, < 4.0.0 → no fix; @nuxt/nitro-server >= 4.2.0, < 4.6.4 → 4.6.4 | >= 3.20.0, < 4.0.0 → no fix; @nuxt/vite-server >= 4.6.0, < 4.6.4 → 4.6.4 · partly fixed
Why tagged?
- SCA from the title:
GHSA-f3x9-2chm-73c8 / CVE-202
- SCA from the title:
GHSA-m9j8-jcmv-hp69 / CVE-2026-128118: SvelteKit: Build-time server-only module import guard could fail, resulting in server secrets being statically replaced in client bundle
@sveltejs/kit >= 3.0.0, <= 3.1.0 → 3.1.1
Why tagged?
- SCA from the title:
GHSA-m9j8-jcmv-hp69 / CVE-202
- SCA from the title:
GHSA-3r8g-jcqq-3p5j / CVE-2026-128120: SvelteKit: DoS while parsing form data from a remote functions `form`
@sveltejs/kit >= 2.42.0, <= 3.1.0 → 3.1.1
Why tagged?
- SCA from the title:
GHSA-3r8g-jcqq-3p5j / CVE-202
- SCA from the title:
GHSA-6cf5-gc4q-fm3x / CVE-2026-128119: SvelteKit: Private `query.batch` functions could collide, producing unexpected parameter / function combinations
@sveltejs/kit >= 2.60.1, <= 3.1.0 → 3.1.1
Why tagged?
- SCA from the title:
GHSA-6cf5-gc4q-fm3x / CVE-202
- SCA from the title:
GHSA-rqp5-r3wg-vg35 / CVE-2026-128116: SvelteKit: Protocol-relative module import during server-side route resolution allows cross-origin script execution
@sveltejs/kit >= 3.0.0, < 3.1.1 → 3.1.1 | < 2.70.4 → 2.70.4
Why tagged?
- SCA from the title:
GHSA-rqp5-r3wg-vg35 / CVE-202
- SCA from the title:
GHSA-grg7-4c3w-pv5j: Malicious code in @xzvbailss/baileys (npm)
@xzvbailss/baileys = 1.0.0 → remove it | = 5.0.0 → remove it | = 6.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-grg7-4c3w-pv5j: Maliciou
- SCA from the title:
GHSA-v63h-mgc2-6vj4: Malicious code in hstdemotests (npm)
hstdemotests = 1.3.0 → remove it
Why tagged?
- SCA from the title:
GHSA-v63h-mgc2-6vj4: Maliciou
- SCA from the title:
GHSA-79jw-734h-5fvr: Malicious code in tg-msg-effect (npm)
tg-msg-effect > 0 → remove it | = 1.0.7 → remove it | = 1.0.8 → remove it | = 1.0.9 → remove it | = 1.0.10 → remove it
Why tagged?
- SCA from the title:
GHSA-79jw-734h-5fvr: Maliciou
- SCA from the title:
GHSA-g3w3-wrvj-rr9w: Malicious code in hstdemotest (npm)
hstdemotest = 1.3.0 → remove it
Why tagged?
- SCA from the title:
GHSA-g3w3-wrvj-rr9w: Maliciou
- SCA from the title:
GHSA-72cg-f236-g9g4: Malicious code in baileys-clean (npm)
baileys-clean = 7.3.2 → remove it
Why tagged?
- SCA from the title:
GHSA-72cg-f236-g9g4: Maliciou
- SCA from the title:
GHSA-h6jf-g8cj-x4v3: Malware in @univerjs-pro/sheets-pivot-chart
@univerjs-pro/sheets-pivot-chart = 1.5.0 → remove it
Why tagged?
- SCA from the title:
GHSA-h6jf-g8cj-x4v3: Malware
- SCA from the title:
GHSA-xxrh-88wg-7qf4: Malware in pmhq-dist-win-x64
pmhq-dist-win-x64 = 9.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-xxrh-88wg-7qf4: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
3 Go security advisories
GHSA-vx32-xf7g-9ghr / CVE-2026-129237: qbee-agent: Docker Compose build context Zip Slip writes outside context directory
go.qbee.io/agent < 0.0.0-20260908095235-eb7875f0a849 → 0.0.0-20260908095235-eb7875f0a849
Why tagged?
- SCA from the title:
GHSA-vx32-xf7g-9ghr / CVE-202
- SCA from the title:
GHSA-gj7r-p794-hhq5 / CVE-2026-129235: Kubeshark: MCP `download_file` writes fetched bytes to an unvalidated destination path
github.com/kubeshark/kubeshark >= 0.0.2-0.20260304171723-eb7dc42b6ea0, < 0.0.2-0.20260812200004-a76a1920dc75 → 0.0.2-0.20260812200004-a76a1920dc75
Why tagged?
- SCA from the title:
GHSA-gj7r-p794-hhq5 / CVE-202
- SCA from the title:
GHSA-8vf2-hxg5-crqh / CVE-2026-129236: Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover
github.com/kubeshark/kubeshark >= 0.0.2-0.20260206182249-0bbbb473ea3f, < 0.0.2-0.20260812200004-a76a1920dc75 → 0.0.2-0.20260812200004-a76a1920dc75
Why tagged?
- SCA from the title:
GHSA-8vf2-hxg5-crqh / CVE-202
- AI Security from the title:
2026-129236: Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → im
- SCA from the title:
All Go advisories · each advisory is independent, not one campaign
7 Packagist security advisories
GHSA-c94f-87xg-65wf / CVE-2026-91115: Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter
silverstripe/framework >= 6.0.0, < 6.2.13 → 6.2.13
Why tagged?
- SCA from the title:
GHSA-c94f-87xg-65wf / CVE-202
- SCA from the title:
GHSA-4qv2-g5vp-wjjw / CVE-2026-91113: Silverstripe Framework: User-controlled ClassName allows unauthorized record type change
silverstripe/framework < 6.2.13 → 6.2.13
Why tagged?
- SCA from the title:
GHSA-4qv2-g5vp-wjjw / CVE-202
- SCA from the title:
GHSA-rg72-5958-c65m / CVE-2026-91112: Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation
silverstripe/framework < 6.2.13 → 6.2.13
Why tagged?
- SCA from the title:
GHSA-rg72-5958-c65m / CVE-202
- SCA from the title:
GHSA-3qh3-54qg-gpq3 / CVE-2026-88989: Silverstripe Framework: Auth bypass GridFieldDetailForm
silverstripe/framework < 6.2.13 → 6.2.13
Why tagged?
- SCA from the title:
GHSA-3qh3-54qg-gpq3 / CVE-202
- SCA from the title:
GHSA-xwg4-8hqh-79jq / CVE-2026-88988: Silverstripe Framework: XSS via SVG data URI
silverstripe/framework < 6.2.13 → 6.2.13
Why tagged?
- SCA from the title:
GHSA-xwg4-8hqh-79jq / CVE-202
- SCA from the title:
GHSA-qqrg-8jpm-8mph / CVE-2026-88987: Silverstripe Framework: XSS via XHTML data URI
silverstripe/framework < 6.2.13 → 6.2.13
Why tagged?
- SCA from the title:
GHSA-qqrg-8jpm-8mph / CVE-202
- SCA from the title:
GHSA-w553-pwx6-3mg9 / CVE-2026-63182: lightsaml allows Signature wrapping bypass
litesaml/lightsaml >= 5.0.0, < 5.0.1 → 5.0.1 | >= 4.0.0, < 4.7.1 → 4.7.1
Why tagged?
- SCA from the title:
GHSA-w553-pwx6-3mg9 / CVE-202
- SCA from the title:
All Packagist advisories · each advisory is independent, not one campaign
24 PyPI security advisories
GHSA-8cgq-x343-p74c / CVE-2026-129301: mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch
mail-parser >= 4.6.0, < 4.6.3 → 4.6.3
Why tagged?
- SCA from the title:
GHSA-8cgq-x343-p74c / CVE-202
- SCA from the title:
GHSA-xhrq-2mqv-q8wx / CVE-2026-129300: mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date
mail-parser >= 3.7.0, < 4.6.3 → 4.6.3
Why tagged?
- SCA from the title:
GHSA-xhrq-2mqv-q8wx / CVE-202
- SCA from the title:
GHSA-24mq-4vc6-2prf / CVE-2026-129299: mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input
mail-parser <= 4.6.1 → 4.6.2
Why tagged?
- SCA from the title:
GHSA-24mq-4vc6-2prf / CVE-202
- SCA from the title:
GHSA-72px-j8gh-p79x / CVE-2026-129297: mail-parser: Sender IP address spoofing in get_server_ipaddress()
mail-parser <= 4.6.1 → 4.6.2
Why tagged?
- SCA from the title:
GHSA-72px-j8gh-p79x / CVE-202
- SCA from the title:
GHSA-r7w7-vpq8-c5vv / CVE-2026-129295: mail-parser is vulnerable to polynomial ReDoS in email header parsing
mail-parser >= 4.2.0, < 4.6.1 → 4.6.1
Why tagged?
- SCA from the title:
GHSA-r7w7-vpq8-c5vv / CVE-202
- SCA from the title:
GHSA-fr3h-cpq2-9496 / CVE-2026-129296: mail-parser: Path Traversal vulnerability in attachment extraction
mail-parser >= 3.8.0, < 4.6.0 → 4.6.0
Why tagged?
- SCA from the title:
GHSA-fr3h-cpq2-9496 / CVE-202
- SCA from the title:
GHSA-259w-wmqg-fp76 / CVE-2026-86046: termux-sync: Arbitrary file write during restore via attacker-controlled manifest source path
termux-sync <= 1.2.3 → 1.2.4
Why tagged?
- SCA from the title:
GHSA-259w-wmqg-fp76 / CVE-202
- SCA from the title:
GHSA-7mxv-7h3q-9324 / CVE-2026-128134: NLTK dot2img runs Graphviz 'dot' without the trusted-exec chokepoint, enabling local code execution via a writable PATH element
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-7mxv-7h3q-9324 / CVE-202
- SCA from the title:
GHSA-jm3w-gw2p-xjfj / CVE-2026-128124: AIOHTTP: Event loop stall in add_domain() wildcard matching
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-jm3w-gw2p-xjfj / CVE-202
- SCA from the title:
GHSA-5pv8-vvhc-h7jv / CVE-2026-128125: AIOHTTP: Unbounded cookie storage in client CookieJar
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-5pv8-vvhc-h7jv / CVE-202
- SCA from the title:
GHSA-xgw8-8ccx-rmqh / CVE-2026-128126: AIOHTTP: Too many URL-encoded form fields block the event loop
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-xgw8-8ccx-rmqh / CVE-202
- SCA from the title:
GHSA-24c4-3p7v-29cm / CVE-2026-128127: AIOHTTP: Base64 multipart parts bypass client_max_size
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-24c4-3p7v-29cm / CVE-202
- SCA from the title:
GHSA-3rp8-rxj8-mvjw / CVE-2026-128128: AIOHTTP: WebSocket max_msg_size bypass via integer overflow
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-3rp8-rxj8-mvjw / CVE-202
- SCA from the title:
GHSA-pw86-h8fm-j323 / CVE-2026-128129: AIOHTTP: Unbounded buffering of data received during an upgrade request
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-pw86-h8fm-j323 / CVE-202
- SCA from the title:
GHSA-28qf-cpwq-vmc2 / CVE-2026-128130: AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-28qf-cpwq-vmc2 / CVE-202
- SCA from the title:
GHSA-h4cc-hm5h-fmm9 / CVE-2026-128131: AIOHTTP: Concatenated compressed streams cause excessive CPU use
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-h4cc-hm5h-fmm9 / CVE-202
- SCA from the title:
GHSA-5rmc-48h2-hvcm / CVE-2026-128132: AIOHTTP: WebSocket receive queue limits bypassed by small or compressed messages
aiohttp <= 3.14.3 → 3.14.4
Why tagged?
- SCA from the title:
GHSA-5rmc-48h2-hvcm / CVE-202
- SCA from the title:
GHSA-xmfg-f9cm-w86q / CVE-2026-126302: NLTK: Symlink escape in chat80.sql_query bypasses the pathsec data-root sandbox to read out-of-root SQLite databases
nltk >= 3.9.4, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-xmfg-f9cm-w86q / CVE-202
- SCA from the title:
GHSA-59f9-gqg8-mqpj / CVE-2026-126296: NLTK: Path Traversal in save_maxent_params / load_maxent_params Allow Arbitrary File READ/WRITE
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-59f9-gqg8-mqpj / CVE-202
- SCA from the title:
GHSA-vxjx-jrjx-wwm8: Malicious code in ldk-node (PyPI)
ldk-node = 0.7.9999 → remove it
Why tagged?
- SCA from the title:
GHSA-vxjx-jrjx-wwm8: Maliciou
- SCA from the title:
GHSA-vgw5-5gvv-4mgw: Malicious code in my-signature (PyPI)
my-signature = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-vgw5-5gvv-4mgw: Maliciou
- SCA from the title:
GHSA-cv98-wccv-mv8p: Malicious code in my-signatureu (PyPI)
my-signatureu = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-cv98-wccv-mv8p: Maliciou
- SCA from the title:
GHSA-v882-m3jg-6xj6: Malicious code in usdm-minting-client (PyPI)
usdm-minting-client = 0.1.2 → remove it | = 0.1.0 → remove it | = 0.1.3 → remove it | = 0.1.1 → remove it
Why tagged?
- SCA from the title:
GHSA-v882-m3jg-6xj6: Maliciou
- SCA from the title:
GHSA-3rjm-5865-523c: Malicious code in my-poc-sandbox (PyPI)
my-poc-sandbox = 1.0.0 → remove it | = 1.0.1 → remove it | = 1.0.2 → remove it
Why tagged?
- SCA from the title:
GHSA-3rjm-5865-523c: Maliciou
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
Threat Landscape of Vibe Coding and the Road to Secure Autonomy
Vibe coding is reshaping software development, enabling faster implementation and allowing individuals with limited programming experience to describe requirements in natural language while AI agents write, test, and deploy the code. As these agents evolve into autonomous…
Why tagged?
- SCA from the excerpt:
secure code generation, supply-chain attacks, and human factors, wit
- AI Security from the excerpt:
across areas including prompt injection, insecure code generati
- SCA from the excerpt:
GHSA-mfr8-8qww-v76h / CVE-2026-119790: Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
next >= 16.3.0, <= 16.4.4 → 16.4.5
Why tagged?
- SCA from the title:
GHSA-mfr8-8qww-v76h / CVE-202
- SCA from the title:
Cursor Supply Chain Attack Started at Fireworks AI
The attacker stole an access key from Fireworks and used it to exfiltrate credentials that enabled them to push malicious Claude Code extension copies.
Why tagged?
- SCA from the title:
Cursor Supply Chain Attack Started at Fireworks AI
- Agentic SDLC from the excerpt:
them to push malicious Claude Code extension copies.
- AI Security from the excerpt:
at enabled them to push malicious Claude Code extension copies.
- SCA from the title:
BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
An investigation into suspicious activity within a Russian software developer's network has uncovered a months-long compromise of its development infrastructure and a software code-signing server. The activity, documented by Kaspersky's ICS CERT team after it was contacted by…
Why tagged?
- SCA from the title:
promises Russian Firm's Code-Signing Server
- SCA from the title:
3 npm security advisories
GHSA-95pv-hv63-58m8: Malware in @theholocron/holocron-plugin-discord
@theholocron/holocron-plugin-discord = 5.0.0-alpha.436 → remove it
Why tagged?
- SCA from the title:
GHSA-95pv-hv63-58m8: Malware
- SCA from the title:
GHSA-2p2h-g9qq-v2wx: Malware in node-zserial
node-zserial = 1.0.42 → remove it
Why tagged?
- SCA from the title:
GHSA-2p2h-g9qq-v2wx: Malware
- SCA from the title:
GHSA-w3gq-mm9x-7w7c: Malware in @crvouga/mockingbird-service-microsoft
@crvouga/mockingbird-service-microsoft = 0.14.0 → remove it
Why tagged?
- SCA from the title:
GHSA-w3gq-mm9x-7w7c: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
2 PyPI security advisories
GHSA-rp2f-46j6-grv4: Malicious code in gatepay-sdk-python (PyPI)
gatepay-sdk-python = 99.99.1 → remove it
Why tagged?
- SCA from the title:
GHSA-rp2f-46j6-grv4: Maliciou
- SCA from the title:
GHSA-8chm-xj53-hg7h: Malicious code in gateio-v4 (PyPI)
gateio-v4 = 99.99.1 → remove it
Why tagged?
- SCA from the title:
GHSA-8chm-xj53-hg7h: Maliciou
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
2 npm security advisories
GHSA-ccgw-9w4v-vqh2: Malicious code in testpackage83 (npm)
testpackage83 = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-ccgw-9w4v-vqh2: Maliciou
- SCA from the title:
GHSA-7jf6-qwv2-qppp: Malware in @sfunction/dsh-screenshot
@sfunction/dsh-screenshot = 0.1.1 → remove it
Why tagged?
- SCA from the title:
GHSA-7jf6-qwv2-qppp: Malware
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
10 PyPI security advisories
GHSA-h6gp-mprh-hhhv: Malicious code in gateio-ws (PyPI)
gateio-ws = 99.99.1 → remove it | = 99.99.2 → remove it
Why tagged?
- SCA from the title:
GHSA-h6gp-mprh-hhhv: Maliciou
- SCA from the title:
GHSA-fmcm-6g66-p65w: Malicious code in ps-bool (PyPI)
ps-bool = 0.2.0 → remove it | = 0.2.1 → remove it | = 0.2.3 → remove it | = 0.2.4 → remove it | = 0.2.5 → remove it
Why tagged?
- SCA from the title:
GHSA-fmcm-6g66-p65w: Maliciou
- SCA from the title:
GHSA-7r7f-5mcw-j79p: Malicious code in demo-pingtest-xyz (PyPI)
demo-pingtest-xyz = 0.0.1 → remove it
Why tagged?
- SCA from the title:
GHSA-7r7f-5mcw-j79p: Maliciou
- SCA from the title:
GHSA-29h4-x5fq-cp34: Malicious code in gateio-client (PyPI)
gateio-client = 99.99.1 → remove it
Why tagged?
- SCA from the title:
GHSA-29h4-x5fq-cp34: Maliciou
- SCA from the title:
GHSA-xjgf-m5q9-6gpf: Malicious code in gateio-sdk (PyPI)
gateio-sdk = 99.99.1 → remove it | = 99.99.2 → remove it
Why tagged?
- SCA from the title:
GHSA-xjgf-m5q9-6gpf: Maliciou
- SCA from the title:
GHSA-fmq9-qj28-89vh: Malicious code in xrfdc (PyPI)
xrfdc = 0.0.0 → remove it | = 2.0 → remove it
Why tagged?
- SCA from the title:
GHSA-fmq9-qj28-89vh: Maliciou
- SCA from the title:
GHSA-9fc6-4mrc-h6pp: Malicious code in trezortranslate (PyPI)
trezortranslate = 0.0.0 → remove it | = 1.0.0 → remove it
Why tagged?
- SCA from the title:
GHSA-9fc6-4mrc-h6pp: Maliciou
- SCA from the title:
GHSA-89p3-fcch-88ph / CVE-2026-126299: NLTK: Quadratic-time CPU denial of service in CCG lexicon parser (fromstring) on wide bracket bodies and operator chains
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-89p3-fcch-88ph / CVE-202
- SCA from the title:
GHSA-r53h-rw34-8h97 / CVE-2026-126298: NLTK: Quadratic-time CPU denial of service in Tree.chomsky_normal_form right-factor binarization via list.pop(0)
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-r53h-rw34-8h97 / CVE-202
- SCA from the title:
GHSA-v8f3-6phw-6mh9 / CVE-2026-126297: NLTK: Quadratic-time CPU denial of service in ConllCorpusReader SRL instance builder via nested span rescan
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-v8f3-6phw-6mh9 / CVE-202
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
Cursor confirms security breach led to malicious Claude Code extension
Cursor confirmed it suffered a security breach that let hackers distribute a malicious Claude Code extension through its marketplace after stealing credentials from AI infrastructure provider Fireworks AI. [...]
Why tagged?
- SCA from the title:
breach led to malicious Claude Code extension
- Agentic SDLC from the title:
breach led to malicious Claude Code extension
- AI Security from the title:
security breach led to malicious Claude Code extension
- SCA from the title:
26 npm security advisories
GHSA-vfc7-g3hx-84wp: Malware in @zread/cli-win32-arm64
@zread/cli-win32-arm64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-vfc7-g3hx-84wp: Malware
- SCA from the title:
GHSA-h7rw-cqm6-8xhc: Malware in @zread/cli-win32-x64
@zread/cli-win32-x64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-h7rw-cqm6-8xhc: Malware
- SCA from the title:
GHSA-4r36-qqxv-mv2c: Malware in @zread/cli-darwin-x64
@zread/cli-darwin-x64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-4r36-qqxv-mv2c: Malware
- SCA from the title:
GHSA-mj52-2x34-ppqq: Malware in @zread/cli-darwin-arm64
@zread/cli-darwin-arm64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-mj52-2x34-ppqq: Malware
- SCA from the title:
GHSA-jw9g-9vcc-5xjv: Malware in @zread/cli-linux-arm64
@zread/cli-linux-arm64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-jw9g-9vcc-5xjv: Malware
- SCA from the title:
GHSA-rmrw-hx84-5hgq: Malware in @zread/cli-linux-x64
@zread/cli-linux-x64 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rmrw-hx84-5hgq: Malware
- SCA from the title:
GHSA-3429-mj25-c5wf: Malware in zread_cli
zread_cli >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-3429-mj25-c5wf: Malware
- SCA from the title:
GHSA-qfx6-q44v-9qqw / CVE-2026-62297: ag-psd can exhaust memory when parsing crafted PSD dimensions
ag-psd < 31.0.0 → 31.0.0
Why tagged?
- SCA from the title:
GHSA-qfx6-q44v-9qqw / CVE-202
- SCA from the title:
GHSA-q78g-75cg-hwq6: Malware in @jelou/cli-win32-x64
@jelou/cli-win32-x64 = 4.26.1 → remove it | = 4.24.0 → remove it
Why tagged?
- SCA from the title:
GHSA-q78g-75cg-hwq6: Malware
- SCA from the title:
GHSA-j4f5-mgch-g6xr: Malware in rush-mfa
rush-mfa >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j4f5-mgch-g6xr: Malware
- SCA from the title:
GHSA-rc56-p7rg-hx63: Malware in dowload_ebok_to_kill_and_kill_again_by_john_coston_id159
dowload_ebok_to_kill_and_kill_again_by_john_coston_id159 >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-rc56-p7rg-hx63: Malware
- SCA from the title:
GHSA-w4x5-gcvx-77p7: Malware in dowload_ebok_aws_lambda_in_action_by_danilo_poccia_o3xgh
dowload_ebok_aws_lambda_in_action_by_danilo_poccia_o3xgh >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-w4x5-gcvx-77p7: Malware
- SCA from the title:
GHSA-pq73-ph36-cv8h: Malware in dowload_ebok_honey_so_sweet_vol_5_by_amu_meguro_6vbdo
dowload_ebok_honey_so_sweet_vol_5_by_amu_meguro_6vbdo >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-pq73-ph36-cv8h: Malware
- SCA from the title:
GHSA-6p5c-33pm-w6g4: Malware in dowload_ebok_ecchi_gallery_by_takumi_kobayashi_c8fuf
dowload_ebok_ecchi_gallery_by_takumi_kobayashi_c8fuf >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-6p5c-33pm-w6g4: Malware
- SCA from the title:
GHSA-8q25-wxxp-pv39: Malware in dowload_ebok_dorothy_debe_morir_by_danielle_paige_4802q
dowload_ebok_dorothy_debe_morir_by_danielle_paige_4802q >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-8q25-wxxp-pv39: Malware
- SCA from the title:
GHSA-j96h-3gpr-89wg: Malware in dowload_ebok_kosten_und_leistungsrechnung_fur_dummies_by_michael_griga_b29bg
dowload_ebok_kosten_und_leistungsrechnung_fur_dummies_by_michael_griga_b29bg >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-j96h-3gpr-89wg: Malware
- SCA from the title:
GHSA-cv7j-v76g-6272: Malware in dowload_ebok_puppy_love_by_rachel_renee_russell_7ae7c
dowload_ebok_puppy_love_by_rachel_renee_russell_7ae7c >= 0 → remove it
Why tagged?
- SCA from the title:
GHSA-cv7j-v76g-6272: Malware
- SCA from the title:
GHSA-mw6w-2fmv-pvw3 / CVE-2026-128117: SvelteKit: adapter-node crashes with an unhandled URIError when `reroute` rewrites malformed pathnames
@sveltejs/kit >= 3.0.0, < 3.1.1 → 3.1.1 | < 2.70.4 → 2.70.4
Why tagged?
- SCA from the title:
GHSA-mw6w-2fmv-pvw3 / CVE-202
- SCA from the title:
GHSA-jf9x-2fg2-hx4w / CVE-2026-128121: SvelteKit: Prerendered paths are interpreted as regular expressions in Vercel route config generated by @sveltejs/adapter-vercel and @sveltejs/adapter-static
@sveltejs/adapter-vercel < 6.3.5 → 6.3.5 | >= 7.0.0-next.0, < 7.0.2 → 7.0.2; @sveltejs/adapter-static >= 4.0.0-next.0, < 4.0.1 → 4.0.1 | < 3.0.11 → 3.0.11
Why tagged?
- SCA from the title:
GHSA-jf9x-2fg2-hx4w / CVE-202
- SCA from the title:
GHSA-5wg4-q3ww-283h / CVE-2026-128122: SvelteKit: Prerendered redirect paths can inject arbitrary rules into the `_redirects` file generated by `@sveltejs/adapter-cloudflare`
@sveltejs/adapter-cloudflare >= 4.7.0, < 7.2.10 → 7.2.10 | >= 8.0.0-next.0, < 8.0.2 → 8.0.2
Why tagged?
- SCA from the title:
GHSA-5wg4-q3ww-283h / CVE-202
- SCA from the title:
GHSA-rqw3-x7hx-mm3p / CVE-2026-128123: SvelteKit: `@sveltejs/adapter-node` crashes when proxying certain requests via `fetch`
@sveltejs/adapter-node >= 5.5.7, < 5.5.8 → 5.5.8 | >= 6.0.0-next.0, < 6.0.1 → 6.0.1
Why tagged?
- SCA from the title:
GHSA-rqw3-x7hx-mm3p / CVE-202
- SCA from the title:
GHSA-r99w-jh2x-3mg9 / CVE-2026-128077: Nuxt: Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routes
@nuxt/nitro-server >= 4.6.0, < 4.6.4 → 4.6.4
Why tagged?
- SCA from the title:
GHSA-r99w-jh2x-3mg9 / CVE-202
- SCA from the title:
GHSA-3v2p-hm54-8qcq / CVE-2026-128080: OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor in @opentelemetry/instrumentation-http
@opentelemetry/instrumentation-http >= 0.204.0, < 0.222.0 → 0.222.0
Why tagged?
- SCA from the title:
GHSA-3v2p-hm54-8qcq / CVE-202
- SCA from the title:
GHSA-mh32-jxcr-mh9f / CVE-2026-126361: Astro: XSS via attribute injection in dynamic tag names
astro <= 7.4.4 → 7.4.5
Why tagged?
- SCA from the title:
GHSA-mh32-jxcr-mh9f / CVE-202
- SCA from the title:
GHSA-r3h5-4585-7x3w / CVE-2026-126364: Astro: Image endpoint in @astrojs/node can read files from a case-variant sibling of the output directory on case-sensitive filesystems
@astrojs/node <= 11.1.11 → no fix; astro >= 5.14.3, <= 7.4.6 → 7.4.7 · partly fixed
Why tagged?
- SCA from the title:
GHSA-r3h5-4585-7x3w / CVE-202
- SCA from the title:
GHSA-mjrq-cffv-q4qc / CVE-2026-128070: Nuxt dev server serves files from a parent directory with a stray lockfile or workspace file
@nuxt/schema >= 3.5.0, < 4.6.4 → 4.6.4
Why tagged?
- SCA from the title:
GHSA-mjrq-cffv-q4qc / CVE-202
- SCA from the title:
All npm advisories · each advisory is independent, not one campaign
11 PyPI security advisories
GHSA-fg9w-wfp5-j933 / CVE-2026-126295: NLTK: BllipParser passes caller-supplied model paths to the bllipparser C extension with no pathsec check, enabling arbitrary read
nltk >= 3.10.0, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-fg9w-wfp5-j933 / CVE-202
- SCA from the title:
GHSA-gpwc-27cw-rh9r: NLTK: Quadratic CPU exhaustion in LegalitySyllableTokenizer.tokenize via unguarded onset reversal loop
nltk >= 3.6, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-gpwc-27cw-rh9r: NLTK: Qu
- SCA from the title:
GHSA-ffr9-mgrr-wcvr / CVE-2026-126300: NLTK: Quadratic CPU exhaustion in TreebankWordTokenizer.span_tokenize via list.pop(0) in quote-restore loop
nltk >= 3.2.5, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-ffr9-mgrr-wcvr / CVE-202
- SCA from the title:
GHSA-8fx7-8jr8-84rv / CVE-2026-126303: NLTK: Unbounded CPU consumption in SteppingRecursiveDescentParser.parse() with ambiguous or self-embedding grammars
nltk <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-8fx7-8jr8-84rv / CVE-202
- SCA from the title:
GHSA-qg35-44qx-7vrr / CVE-2026-126304: NLTK: Symlink escape in YCOECorpusReader lets a psd/pos directory symlink read files outside the corpus root within the data sandbox
nltk >= 3.10.0, <= 3.10.3 → 3.10.4
Why tagged?
- SCA from the title:
GHSA-qg35-44qx-7vrr / CVE-202
- SCA from the title:
GHSA-5cjw-f85j-cv6r / CVE-2026-126347: Tornado: Open redirect via triple-slash redirect paths
tornado <= 6.6.0 → 6.6.1
Why tagged?
- SCA from the title:
GHSA-5cjw-f85j-cv6r / CVE-202
- SCA from the title:
GHSA-vvf4-9x63-8xvv / CVE-2026-128089: dnspython has excessive memory and CPU use
dnspython < 2.9.2 → 2.9.2
Why tagged?
- SCA from the title:
GHSA-vvf4-9x63-8xvv / CVE-202
- SCA from the title:
GHSA-jv6m-48w5-5rpr / CVE-2026-128079: envd: Host file disclosure through requirements path traversal and TOCTOU
envd >= 0.3.38, < 1.3.6 → 1.3.6
Why tagged?
- SCA from the title:
GHSA-jv6m-48w5-5rpr / CVE-202
- SCA from the title:
GHSA-mf5v-w3w3-f6cg / CVE-2026-126360: OpenTelemetry Python API: Denial of service through quadratic-time traceparent parsing
opentelemetry-api <= 1.45.1 → 1.45.2
Why tagged?
- SCA from the title:
GHSA-mf5v-w3w3-f6cg / CVE-202
- SCA from the title:
GHSA-6655-6qjp-jx7x / CVE-2026-126191: Soup Sieve: Exponential ReDoS in selector compilation via \9-run in CSS_ESCAPES/IDENTIFIER
soupsieve <= 2.10 → 3.0.2
Why tagged?
- SCA from the title:
GHSA-6655-6qjp-jx7x / CVE-202
- SCA from the title:
GHSA-7g44-g9rc-x53w / CVE-2026-126193: Soup Sieve: Uncontrolled recursion in CSS parser lets nested pseudo-class selectors exhaust the Python call stack
soupsieve >= 0.4, <= 2.10 → 3.0.2
Why tagged?
- SCA from the title:
GHSA-7g44-g9rc-x53w / CVE-202
- SCA from the title:
All PyPI advisories · each advisory is independent, not one campaign
3 Go security advisories
GHSA-pp88-jhwj-5qh5 / CVE-2026-62683: File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths
github.com/filebrowser/filebrowser/v2 < 2.63.17 → 2.63.17
Why tagged?
- SCA from the title:
GHSA-pp88-jhwj-5qh5 / CVE-202
- SCA from the title:
GHSA-rrfc-gjm9-cgrj / CVE-2026-128086: OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification
go.opentelemetry.io/otel/baggage >= 1.0.0-RC1, < 1.47.0 → 1.47.0; go.opentelemetry.io/otel/propagation >= 1.0.0-RC1, < 1.47.0 → 1.47.0
Why tagged?
- SCA from the title:
GHSA-rrfc-gjm9-cgrj / CVE-202
- SCA from the title:
GHSA-q7gw-24fr-5p69 / CVE-2026-128085: opentelemetry-go: AttributeValueLengthLimit is fully bypassed by attribute values composed of valid U+FFFD runes
go.opentelemetry.io/otel/sdk >= 1.33.0, < 1.47.0 → 1.47.0; go.opentelemetry.io/otel/sdk/log >= 0.9.0, < 1.47.0 → 1.47.0; go.opentelemetry.io/otel/trace >= 1.35.0, < 1.47.0 → 1.47.0
Why tagged?
- SCA from the title:
GHSA-q7gw-24fr-5p69 / CVE-202
- SCA from the title:
All Go advisories · each advisory is independent, not one campaign
2 NuGet security advisories
GHSA-6vhm-j9h7-f9gh / CVE-2026-128082: AutoMapper: Uncontrolled Recursion with Constructor Parameters
AutoMapper >= 16.0.0, < 16.3.0 → 16.3.0 | < 15.1.4 → 15.1.4
Why tagged?
- SCA from the title:
GHSA-6vhm-j9h7-f9gh / CVE-202
- SCA from the title:
GHSA-gpwp-5797-mjff / CVE-2026-128081: AutoMapper: Denial of Service via uncontrolled recursion that bypasses MaxDepth
AutoMapper >= 16.0.0, < 16.3.0 → 16.3.0 | < 15.1.4 → 15.1.4
Why tagged?
- SCA from the title:
GHSA-gpwp-5797-mjff / CVE-202
- SCA from the title:
All NuGet advisories · each advisory is independent, not one campaign
2 crates.io security advisories
GHSA-9264-jvgf-6w2f / CVE-2026-128087: russh kex_done: Shared-secret callback runs before server host-key verification
russh >= 0.55.0, < 0.65.1 → 0.65.1
Why tagged?
- SCA from the title:
GHSA-9264-jvgf-6w2f / CVE-202
- SCA from the title:
GHSA-736f-c93q-9fwx / CVE-2026-128088: russh try_sign: asynchronous confirmation can sign after agent lock
russh = 0.65.0 → 0.65.1
Why tagged?
- SCA from the title:
GHSA-736f-c93q-9fwx / CVE-202
- SCA from the title:
All crates.io advisories · each advisory is independent, not one campaign
3 RubyGems security advisories
GHSA-4fqr-96q8-xrfx / CVE-2026-128084: sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger
sqlite3 <= 2.10.1 → 2.10.2
Why tagged?
- SCA from the title:
GHSA-4fqr-96q8-xrfx / CVE-202
- SCA from the title:
GHSA-h7wh-q2qr-458c / CVE-2026-128069: rails-html-sanitizer: Possible XSS via shared scrubber state in concurrent calls
rails-html-sanitizer < 1.7.2 → 1.7.2
Why tagged?
- SCA from the title:
GHSA-h7wh-q2qr-458c / CVE-202
- SCA from the title:
GHSA-cpgf-5mjf-73p7 / CVE-2026-128068: rails-html-sanitizer: Possible regular expression denial of service with certain configurations
rails-html-sanitizer >= 1.0.3, < 1.7.2 → 1.7.2
Why tagged?
- SCA from the title:
GHSA-cpgf-5mjf-73p7 / CVE-202
- SCA from the title:
All RubyGems advisories · each advisory is independent, not one campaign
1 Packagist security advisory
GHSA-63hm-g96r-2m2q / CVE-2026-128083: Laravel: Task Output Injection - Concurrency Process
laravel/framework < 12.71.0 → 12.71.0 | >= 13.0.0, < 13.40.0 → 13.40.0
Why tagged?
- SCA from the title:
GHSA-63hm-g96r-2m2q / CVE-202
- SCA from the title:
All Packagist advisories · each advisory is independent, not one campaign
Hackers compromise 4,800 GitHub accounts to steal cloud credentials
A new campaign dubbed 'wfx-loot' has unfolded on GitHub where threat actors used 4,837 compromised accounts to probe 61,764 repositories, open pull requests, and push secrets-stealing malware. [...]
Why tagged?
- SCA from the title:
ackers compromise 4,800 GitHub accounts to steal cloud credenti
- SCA from the title:
Trained to betray: How post-training supply chain attacks hijack coding agents
Microsoft Defender Research and the AI Red Team discuss how poisoned datasets and poisoned model checkpoints can trigger remote code execution and other malicious activities.
Why tagged?
- SCA from the title:
tray: How post-training supply chain attacks hijack coding agents
- Agentic SDLC from the title:
ly chain attacks hijack coding agents
- Models from the excerpt:
scover and misuse tools Model poisoning: Building reliable backdoors that persist and trans
- AI Security from the title:
ng supply chain attacks hijack coding agents
- SCA from the title:
VU#685399: PromZard context key code injection leads to remote code execution
Overview The npm library promzard , versions 4.0.0 and earlier, is vulnerable to remote code execution due to direct string interpolation of context object keys, which allows unsanitized JavaScript code injection. Description promzard is a Node.js library designed to automate…
Why tagged?
- SCA from the excerpt:
Overview The npm library promzard , vers
- SCA from the excerpt:
WFX Phantom: The GitHub Actions Secret Stealer That Deletes Its Tracks
A coordinated botnet of compromised GitHub accounts launched a widespread attack, opening seemingly harmless pull requests before pushing a malicious shell script directly to default branches. The script, dubbed "wfx", executed through GitHub Actions to steal secrets before the…
Why tagged?
- SCA from the title:
WFX Phantom: The GitHub Actions Secret Stealer That Del
- SCA from the title:
The AI Security Gap Hiding in Routine Maintenance
AI coding tools are speeding up software development and adding external dependencies faster than teams can review them. Discover why routine maintenance and component updates have become the hidden security gap for organizations today.
Why tagged?
- SCA from the excerpt:
’ll probably hear about supply chain attacks or prompt injection fir
- AI Security from the excerpt:
supply chain attacks or prompt injection first. The Linux Founda
- SCA from the excerpt:
Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor
Compromised maintainer accounts pushed malicious @ethersphere/bee-js 13.3.0 and Swarm Desktop 0.56.2, reusing SleepyDuck’s Ethereum-addressed C2 infrastructure.
Why tagged?
- SCA from the title:
Malicious bee-js npm Release and Swarm Deskt
- SCA from the title:
Announcing Zarf 1.0: Security and Stability for Airgap Software Delivery
Zarf 1.0 is here, bringing the v1beta1 schema, stronger package signing, and improved stability for air-gapped and constrained software delivery environments.
Why tagged?
- SCA from the excerpt:
ed the application, the dependencies, all of the provenance
- SCA from the excerpt:
Agents of Chaos: A Systematization of Knowledge (SoK) on Malicious Attacks on Agentic AI Systems
Agentic AI systems extend large language models with tools, memory, retrieval, browser or computer-use interfaces, code execution, external services, and multi-agent coordination. Although these capabilities enable agents to act beyond text generation and perform tasks, they…
Why tagged?
- SCA from the excerpt:
romised skills, mutable dependencies, or malicious code.
- SCA from the excerpt:
Free Certified Patch for Critical Rails Active Storage Vulnerability
Socket has released a free Certified Patch for a critical Rails Active Storage vulnerability, giving developers time to upgrade to a secure Rails version.
Why tagged?
- SCA from the excerpt:
lnerability, tracked as GHSA-f3w6-w445-fwh9 (CVSS 9.8
- Remediation from the title:
Free Certified Patch for Critical Rails Acti
- SCA from the excerpt:
Shai-Hulud Descendant Surfaces in Malicious Ruby Gem That Steals Credentials and Poisons AI Tools
A malicious Ruby gem runs a credential-stealing worm during installation, poisons AI coding tools, and can wipe files when a stolen GitHub token is revoked.
Why tagged?
- SCA from the title:
t Surfaces in Malicious Ruby Gem That Steals Credentials
- SCA from the title:
PyPI's redesigned project pages with clearer security signals are now live
In July, we announced a series of planned updates to the PyPI user interface. Shaped by user research with members of the Python community , the updates aim to improve how we surface security signals and display package details. We're pleased to share that this work is now…
Why tagged?
- SCA from the excerpt:
f the Python ecosystem, PyPI has become an increasin
- Trust from the excerpt:
it came from). However, provenance and attestations are still unfamiliar co
- SCA from the excerpt:
GitHub to Block pull_request_target Workflows by Default Starting December 2
GitHub is tightening GitHub Actions security with new restrictions on privileged pull request workflows. Here's what changes and how maintainers are affected.
Why tagged?
- SCA from the excerpt:
Hub will begin blocking GitHub Actions workflows triggered by
- SCA from the excerpt:
PolinRider Loader Reappears in Hijacked npm Packages
TL;DR Sonatype Research Labs identified concealed runtime loaders in 12 npm releases across 10 hijacked packages. All 12 releases contain loaders designed to decode payload-server IP addresses from Ethereum transactions sent by the same hard-coded wallet previously reported in…
Why tagged?
- SCA from the title:
r Reappears in Hijacked npm Packages
- SCA from the title:
Malicious Files: Find What Supply Chain Attacks Leave Behind in Your GitHub Repositories and on Developer Machines
StepSecurity Malicious Files finds files planted by Miasma, Shai-Hulud and other supply chain attacks in GitHub repositories and on developer machines.
Why tagged?
- SCA from the title:
icious Files: Find What Supply Chain Attacks Leave Behind in Your Gi
- SCA from the title:
When trust becomes the payload: Inside the threats, etc quarterly report
The newest threats, etc report details how adversaries are weaponizing trust across the entire enterprise stack, abusing everything from AI assistants and npm supply chains to identity flows and legitimate management tools.
Why tagged?
- SCA from the excerpt:
from AI assistants and npm supply chains to identi
- SCA from the excerpt:
Hardening GitHub Actions Against Outside Threats
A practical guide to securing GitHub Actions against supply chain attacks, covering malicious pull requests, credential theft, dependency risks, and release pipelines.
Why tagged?
- SCA from the excerpt:
The supply chain attacks that defined 2025 and 2
- SCA from the excerpt:
AI supply chain attacks: Old payloads, new entry points
AI didn't invent new supply-chain attacks. It opened new paths to old ones.
Why tagged?
- SCA from the title:
AI supply chain attacks: Old payloads, new entr
- Agentic SDLC from the excerpt:
rying to build to an AI coding assistant and get code, dependenc
- SCA from the title:
Stop Chasing CVEs: Start Governing Software Dependencies
A new vulnerability disclosure can set off a familiar chain of work. You check whether or not an application uses the affected component, determine whether the vulnerable code is reachable, find a fixed version, test the upgrade, and get it into production. Then the next…
Why tagged?
- SCA from the title:
tart Governing Software Dependencies
- Remediation from the excerpt:
de is reachable, find a fixed version, test the upgrade, and
- Trust from the title:
top Chasing CVEs: Start Governing Software Dependencies
- SCA from the title:
Composer 2.11 Adds Dependency Cooldowns
Composer 2.11 adds dependency cooldowns, joining package managers that delay new releases to reduce supply chain risks while allowing urgent security updates.
Why tagged?
- SCA from the title:
Composer 2.11 Adds Dependency Co
- SCA from the title:
Fixed Detectors, Moving Code: How Well Do Static Security Analyzers Hold Up over a Decade of C/C++ Evolution?
Static application security testing (SAST) tools are often deployed on the assumption that detectors configured today will remain effective on future code, including previously unknown vulnerabilities. We test this assumption using 20,000 vulnerable and fixed C/C++ cases from…
Why tagged?
- SAST from the excerpt:
ation security testing (SAST) tools are often deploy
- SCA from the excerpt:
C/C++ cases from 1,116 open-source projects (2016-2025), evaluated
- SAST from the excerpt:
Security notice — malicious version of Anthropic.claude-code (2.1.312 and 2.1.313) identified in the Cursor VS Code Extension Marketplace
Today we identified a security incident involving a specific extension in the Cursor VS Code Extension Marketplace: Anthropic.claude-code version 2.1.312 and 2.1.313 for Windows and MacOS.
Why tagged?
- SCA from the title:
dentified in the Cursor VS Code Extension Marketplace
- Agentic SDLC from the excerpt:
extension in the Cursor VS Code Extension Marketplace: Anthropic.claude-code version 2.1
- SCA from the title:
A Supply Chain Attack Put Malicious Anthropic Claude Extensions on Thousands of Devices
Thanks to a lucky break, flawed code in a tainted Claude extension prevented the attacker from fully worming their way into some 5,000 developer machines.
Why tagged?
- SCA from the title:
A Supply Chain Attack Put Malicious Anthropic
- Agentic SDLC from the title:
in Attack Put Malicious Anthropic Claude Extensions on Thousands of Device
- SCA from the title:
Mend SCA now supports Bun, with reachability built in
Mend SCA scans bun.lock and bun.lockb with reachability analysis built in.
Why tagged?
- SCA from the excerpt:
It detects direct and transitive dependencies automatica
- Agentic SDLC from the excerpt:
vaScript developers. AI coding agents increasingly choose Bun
- SCA from the excerpt:
Prioritize Dependabot alerts with reachability analysis
Dependabot alerts can add up faster than a team can work through them. A vulnerable package in your dependency tree doesn’t always mean your code uses the vulnerable part of…
Why tagged?
- SCA from the excerpt:
nerable package in your dependency tree doesn’t always mea
- Remediation from the excerpt:
of your application to prioritize and remediate dependency vulnerabili
- SCA from the excerpt:
This Shit is Hard: Nobody has ever been pwned by Helvetica…or have they?
Fonts are an overlooked software supply chain risk. Learn how Chainguard rebuilt thousands of fonts from source to improve security and trust.
Why tagged?
- SCA from the excerpt:
Fonts are an overlooked software supply chain risk.
- SCA from the excerpt:
litellm 1.107.0 Compromised on PyPI and Docker: Credential Stealer and Hourly Remote Code Loader
litellm 1.107.0 PyPI wheels and Docker images shipped a .pth credential stealer and an hourly remote code loader that exfiltrate to litellm.dev. Analysis, IOCs, and how to respond.
Why tagged?
- SCA from the title:
1.107.0 Compromised on PyPI and Docker: Credential
- SCA from the title:
eMudhra / emSign CA Compromise: What Python, pip, and CI/CD Users Need to Update
Compromised eMudhra intermediate CA keys put Python dependency downloads at risk. Here are the affected tools, verified certificate-trust results, and remediation steps for pip, uv, virtual environments, and CI/CD images.
Why tagged?
- SCA from the excerpt:
iate CA keys put Python dependency downloads at risk.
- SCA from the excerpt:
Graphalgo campaign moves upstream into infrastructure as code
First reported by ReversingLabs in February, the malware has moved to Terraform providers and Go modules. Here’s what you need to know.
Why tagged?
- SCA from the excerpt:
Terraform providers and Go modules.
- SCA from the excerpt:
LiteLLM supply chain compromise: What you need to know
Malicious releases of LiteLLM v1.107.0 were published to PyPI and container registries following multiple maintainer account compromises.
Why tagged?
- SCA from the excerpt:
107.0 were published to PyPI and container registrie
- SCA from the excerpt:
LiteLLM Compromised, Steals Credentials
In a new incident, a malicious version (1.107.0) of the LiteLLM package was uploaded to PyPI and Docker on October 21. The malicious version includes a credential stealer targeting browser, cloud and AI secrets as well as a dormant C2 capability.
Why tagged?
- SCA from the excerpt:
package was uploaded to PyPI and Docker on October 2
- SCA from the excerpt:
Dependabot alerts REST API now includes dependency versions
You can now get the version of a vulnerable dependency directly from Dependabot alert responses in the REST API. Each alert’s dependency object includes a new version_requirement field with the…
Why tagged?
- SCA from the excerpt:
version of a vulnerable dependency directly from Dependabo
- SCA from the excerpt:
GitHub package firewall in public preview
Editor’s note (October 21, 2026): Rewrote the changelog for clarity and added imagery. There’s been a recent flood of malware attacks that exploit systems at package installation time. Agents and…
Why tagged?
- SCA from the excerpt:
ks because they install dependencies to accomplish a task or
- SCA from the excerpt:
Open source license compliance generally available
Enterprises can now manage their dependencies’ licenses at scale with sophisticated, ruleset-based checks that enforce a centralized policy. Open source license compliance is now generally available for GitHub Enterprise Cloud…
Why tagged?
- SCA from the excerpt:
es can now manage their dependencies’ licenses at scale with
- SCA from the excerpt:
VulnBump: Can AI Agents Fix Vulnerable Dependencies Without Breaking the Build?
VulnBump tests AI agents on 307 real dependency upgrades. A fix counts only if the vulnerability is gone and the build and tests stay green.
Why tagged?
- SCA from the title:
I Agents Fix Vulnerable Dependencies Without Breaking the Bu
- Remediation from the title:
VulnBump: Can AI Agents Fix Vulnerable Dependencies Without
- SCA from the title:
Package managers have an integrity problem
I tested 25 of the most popular package managers to check whether they detect a compromised package repository injecting malicious code into legitimate packages. This code integrity problem could be solved using cryptographic hashes or signatures, but many package managers are…
Why tagged?
- SCA from the title:
Package managers have an integrity probl
- SCA from the title:
X.js: A Live Benchmark for Node.js Taint-Style Vulnerabilities
JavaScript vulnerabilities in npm packages pose a significant risk to the Node$.$js ecosystem, and a growing body of work aims to detect, exploit, and mitigate them. Studying and evaluating this work requires up-to-date collections of real vulnerabilities, yet the most commonly…
Why tagged?
- SCA from the excerpt:
ript vulnerabilities in npm packages pose a signifi
- Remediation from the excerpt:
and, when available, a patched version of the package.
- SCA from the excerpt:
And another Tool!
See the Tools page for more info Pitloom automates the generation of SPDX 3-compliant Software Bills of Materials (SBOMs) for Python applications and AI models. It extracts metadata directly from common Python build backends (Flit, Hatchling, PDM, Poetry, setuptools, and…
Why tagged?
- SCA from the excerpt:
Action, Pitloom embeds SBOMs directly into your whee
- AI-BOM from the excerpt:
mates the generation of SPDX 3-compliant Software Bills of Materials (SBOMs) for Python applications and AI models. It extracts metadata d
- SCA from the excerpt:
Auditing the auditor: Unmasking Apex Accelerator
REF8801 exposes how Apex Accelerator combines convincing Web3 services with malicious npm packages, attacker-controlled AI infrastructure, and cross-platform malware delivery.
Why tagged?
- SCA from the excerpt:
identified a malicious npm package, @apexacc/cli ,
- Agentic SDLC from the excerpt:
repackaged a legitimate coding agent to send model requests
- AI Security from the excerpt:
repackaged a legitimate coding agent to send model requests through attacker-controlled services,
- SCA from the excerpt:
Tensorlake npm Package Compromised: A Worm With a Hostage Token That Wipes Your Machine If You Revoke It
The malicious release was built from the project's own main branch and published with an npm provenance attestation.
Why tagged?
- SCA from the title:
Tensorlake npm Package Compromised: A
- Trust from the excerpt:
d published with an npm provenance attestation.
- SCA from the title:
Post-Quantum Cryptography for Sigstore
Future-Proofing Software Supply Chain Security: Post-Quantum Cryptography for Sigstore Post-quantum cryptography (PQC) is rapidly transitioning from a theoretical exploration to an immediate infrastructure necessity. With recent advancements accelerating the estimated arrival…
Why tagged?
- SCA from the excerpt:
Future-Proofing Software Supply Chain Security: Post-Quantum
- Trust from the title:
uantum Cryptography for Sigstore
- SCA from the excerpt:
Sckit Supply Chain Worm Hits MemTensor npm & PyPi scopes
Compromised MemTensor npm releases turn an AI memory plugin into a credential-harvesting entry point, exposing prompts and creating a path to further package compromise.
Why tagged?
- SCA from the title:
ain Worm Hits MemTensor npm & PyPi scopes
- SCA from the title:
Securing the Kubernetes Supply Chain: Introducing WizOS Helm Charts
Secure your Kubernetes supply chain with WizOS Helm Charts. Eliminate hidden CI/CD risks and unmaintained dependencies with hardened, signed, and CVE-scanned charts for seamless Kubernetes deployment.
Why tagged?
- SCA from the excerpt:
risks and unmaintained dependencies with hardened, signed,
- SCA from the excerpt:
Restrospective: How Malicious Updates Poison Your Environment
This post-mortem on recent supply chain attacks and threat actors including S1ngularity, Shai-Hulud and TeamPCP can help you prepare for what comes next.
Why tagged?
- SCA from the excerpt:
s post-mortem on recent supply chain attacks and threat actors inclu
- SCA from the excerpt:
Malicious npm campaign targets developers integrating Twilio
The package poses as a security tool targeting developers looking to implement Internet-based apps with telecom networks.
Why tagged?
- SCA from the title:
Malicious npm campaign targets develo
- SCA from the title:
Be alert: targeted attacks on prominent Rustaceans
Be alert: targeted attacks on prominent Rustaceans Important warning from Adam Harvey and the crates security team: We believe that there is an ongoing campaign targeting rust-lang members and owners of popular crates that is attempting to compromise devices and accounts in…
Why tagged?
- SCA from the excerpt:
as used in a successful supply chain attack against the array ref c
- SCA from the excerpt:
The extension you never installed: KREMLIN forges Chrome's own integrity checks to steal banking sessions
Elastic Security Labs tracked this malicious browser extension across seven campaigns and 15 months, through Brazilian bank lures and the Ethereum smart contracts that hold its C2 configuration.
Why tagged?
- SCA from the excerpt:
they built a malicious browser extension that installs itself in
- SCA from the excerpt:
SPDX Articles in Journal of Innovation
Bob Martin did a great job getting two articles into the August 2026 Journal of Innovation that explore how SPDX can help make supply-chain information more trustworthy, usable, and actionable. “Regulatory Digital Product Passports as a Catalyst for U.S. Supply Chain…
Why tagged?
- SCA from the excerpt:
assessments – including SBOM and AI-BOM information.
- AI-BOM from the excerpt:
ts – including SBOM and AI-BOM information. Read both
- Trust from the excerpt:
rust framework can turn AI governance, digital-twin, and regu
- SCA from the excerpt:
Get the Spectra Assure Community Plugin for JFrog Artifactory
Package managers auto-pull the latest OSS version — malware included. Protect your pipelines with this free plugin.
Why tagged?
- SCA from the excerpt:
Package managers auto-pull the latest OS
- SCA from the excerpt:
Unmasking TeamPCP, King of Software Supply Chain Attacks
Hacker News: 5 points, 0 comments.
Why tagged?
- SCA from the title:
asking TeamPCP, King of Software Supply Chain Attacks
- SCA from the title:
OpenClaw went viral. Meet the maintainers building and securing it.
OpenClaw is the fastest-growing project in GitHub history. Peter Steinberger and several maintainers share what they learned in the project's first six months.
Why tagged?
- SCA from the excerpt:
code review, addressing software supply chain risks, and balancing po
- SCA from the excerpt:
The State of Open Source Supply Chain Attacks
StepSecurity threat intelligence tracked 56 open source supply chain attacks from August 2025 to August 2026, roughly one every three days since March. See the data and the defenses.
Why tagged?
- SCA from the title:
he State of Open Source Supply Chain Attacks
- SCA from the title:
Rust Supply-Chain Attack: arrayref, internment, and append-only-vec Poisoned by the proc-macro1 Build-Time Dropper
Three Rust crates are compromised: arrayref 0.3.10, internment 0.8.7, and append-only-vec 0.1.9 each added a typosquatted build-time dependency (proc-macro1, proc-macro-en) whose build script downloads and runs a remote binary during cargo build. Full technical analysis:…
Why tagged?
- SCA from the title:
Rust Supply-Chain Attack: arrayref, internment,
- SCA from the title:
The security signal log tailing can't see: tracking npm cooldown removals with Elastic Agent
A 40-line CEL integration snapshots .npmrc files every 6 hours to catch cooldown removals. This post walks through the three ways we broke filestream before landing on snapshot semantics.
Why tagged?
- SCA from the excerpt:
npm's min-release-age setti
- SCA from the excerpt:
How we took malware advisories beyond npm
GitHub malware advisories no longer stop at npm. Here's how we wired OpenSSF's malicious-packages data into the Advisory Database, and why we built the pipeline paranoid.
Why tagged?
- SCA from the title:
lware advisories beyond npm
- SCA from the title:
A First Look at Evo Agentic AppSec: Agentic Remediation and Malicious Code Defense
Explore Snyk’s first Agentic AppSec capabilities: an autonomous Remediation Agent that fixes vulnerabilities and Malicious Code Defense that blocks risky packages before they ship.
Why tagged?
- SCA from the excerpt:
cious Code Defense that blocks risky packages before they ship.
- Agentic SDLC from the excerpt:
autonomous Remediation Agent that fixes vulnerabilities and Malicious Code D
- Remediation from the title:
A First Look at Evo Agentic AppSec: Agentic Remediation and Malicious Code D
- SCA from the excerpt:
Inside the keyv npm Compromise: preinstall Malware, Trusted Provenance, and IDE Hooks
keyv 6.0.0 and ten related npm releases shipped install-time malware. See affected versions, hashes, detection steps, and safe remediation order.
Why tagged?
- SCA from the title:
Inside the keyv npm Compromise: preinstall
- SCA from the title:
'ChainDrop' worm compromises hundreds of popular npm packages
On August 4, 2026, several popular npm packages, including 'keyv', were compromised to deliver malware.
Why tagged?
- SCA from the title:
ses hundreds of popular npm packages
- SCA from the title:
Don't Trust the AI Ecosystem: Analyzing Privacy Leakage in Compromised Open-Source Components
Existing model inversion (MI) attacks predominantly rely on post-training optimization to recover private data from model outputs. However, these methods are fundamentally constrained by the target model's generalization bottleneck, often yielding generic features rather than…
Why tagged?
- SCA from the title:
Leakage in Compromised Open-Source Components
- Models from the excerpt:
Existing model inversion (MI) attacks predominan
- SCA from the title:
Anatomy of a Frontier Lab Agent Intrusion: A Technical Timeline of the July 2026 Incident
Anatomy of a Frontier Lab Agent Intrusion: A Technical Timeline of the July 2026 Incident Hugging Face just released this extremely detailed technical description of OpenAI's recent accidental cyberattack against their infrastructure . This attack was very sophisticated, and…
Why tagged?
- SCA from the excerpt:
iting a zero-day in the package registry cache proxy, one of its
- AI Security from the excerpt:
f the attack: [...] the agent escaped its sandbox by exploiting a zero-da
- SCA from the excerpt:
End of list · 896 developments in the last 120 days


























