Security
Microsoft security updates and public advisory evidence: affected products, fixing updates, exploitation and source coverage.
Advisory catalog
Public source statements across vendors. Explicit aliases connect records; each publisher keeps its own state, severity and affected-version evidence.
Collected statements
694341 source statements · aliases may refer to the same vulnerabilityMalicious code in event-bus-lite-testmetest (npm)
osv ·
npm: event-bus-lite-testmetest
Malicious code in ing-feat-itsme-oidc-authentication (npm)
osv ·
npm: ing-feat-itsme-oidc-authentication
Malicious code in @futurae-public/adaptive-js (npm)
osv ·
npm: @futurae-public/adaptive-js
Malicious code in @fcsmc/commercial-analytics (npm)
osv ·
npm: @fcsmc/commercial-analytics
Malicious code in @fmr-ap153177/apex-kit-icons (npm)
osv ·
npm: @fmr-ap153177/apex-kit-icons
Malicious code in @jm-telefonica/multibrand-components (npm)
osv ·
npm: @jm-telefonica/multibrand-components
Malicious code in @fmr-ap149494/apex-base-component (npm)
osv ·
npm: @fmr-ap149494/apex-base-component
Malicious code in @generic-means/ing-feat-scanner-libs (npm)
osv ·
npm: @generic-means/ing-feat-scanner-libs
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.