Loading vulnerability…
CVE-2026-46412 describes a software supply-chain compromise affecting the npm package @beproduct/nestjs-auth, a NestJS authentication module for BeProduct IDS with OpenID Connect support. Between 2026-05-11 20:19 UTC and 22:56 UTC, 18 malicious package versions, 0.1.2 through 0.1.19, were published using a compromised npm publish token. These versions contained a malicious postinstall payload that executed during package installation and attempted to harvest secrets from the installation environment. Targeted data included npm authentication tokens, GitHub personal access and OAuth tokens, GitHub Actions OIDC tokens, AWS credentials from environment variables and local credential files, HashiCorp Vault tokens, and other secrets exposed through environment variables or configuration files. Version 0.1.20 was identified as a clean republish of the original 0.1.1 source tree.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.