Malicious code in epic-web-payment-management-iframe (npm)
osv ·
npm: epic-web-payment-management-iframe
No access to your tenant or devices. Every item links to its source. What this means
Microsoft security updates and public advisory evidence: affected products, fixing updates, exploitation and source coverage.
Public source statements across vendors. Explicit aliases connect records; each publisher keeps its own state, severity and affected-version evidence.
osv ·
npm: epic-web-payment-management-iframe
osv ·
npm: epic-web-payment-management
osv ·
npm: epic-web-payment-management-sandbox
cve-program ·
https://github.com/wildfly/wildfly: wildfly · https://access.redhat.com/jbossnetwork/restricted/listSoftware.html: org.wildfly.security/wildfly-elytron · https://access.redhat.com/downloads/content/package-browser/: eap7-glassfish-el
osv · CVE-2026-86250
npm: h3
osv · CVE-2026-92081
npm: fastify
osv · CVE-2026-84428
npm: fastify
osv · CVE-2026-93981
npm: hono
osv · CVE-2026-76169
npm: fastify
osv · CVE-2026-84469
npm: fastify
osv · CVE-2026-102821
crates.io: russh
osv · CVE-2026-102820
crates.io: pageant
osv · CVE-2026-84504
npm: fastify
osv · CVE-2026-102984
npm: @astrojs/node
osv · CVE-2026-102823
crates.io: russh
osv · CVE-2026-102983
npm: @astrojs/netlify
osv · CVE-2026-102822
crates.io: russh
osv · CVE-2026-102824
crates.io: russh
osv · CVE-2026-102825
crates.io: russh
cve-program ·
Vendor product: OpenDKIM
cve-program ·
Vendor product: laravel-crm
cve-program ·
Vendor product: laravel-crm
cve-program ·
Vendor product: nezha
cve-program ·
Vendor product: obot
cve-program ·
Vendor product: obot
cve-program ·
Vendor product: StarTraining
cve-program ·
Vendor product: CloudClassroom-PHP-Project
cve-program ·
Vendor product: CloudClassroom-PHP-Project
cve-program ·
Vendor product: python-utcp
cve-program ·
Vendor product: HELO Plus
cve-program ·
Vendor product: Tapo C200 · Vendor product: Tapo C100 v5 · Vendor product: Tapo C425 v1.2
A catalog match establishes published evidence, not applicability to your environment. Check resolved package dependencies, or open a Microsoft CVE for fixing KBs, releases and planning.