GCVE-110-OSM-2026-13405

The package declares a `preinstall` script that runs `beacon.js`, which performs a DNS lookup and HTTPS GET to a hardcoded Interactsh collector host (`db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`) at `npm install` time. Both the DNS query and the HTTPS request embed the package name, so any machine that resolves and installs this scoped name sends an unsolicited out-of-band callback carrying the installing host's source IP, resolver identity, timing, and the internal package name to a third-party collector. The implausibly high `99.0.0` version against a scoped name is the dependency-confusion shape — the artifact is intended to win resolution against an internal `@dransay/secrets` and beacon from whichever build environment resolves it, disclosing internal network and build-system identity. No functional library code accompanies the beacon; the package's only on-install effect is the callback. ENTRY beacon.js (install-hook: node beacon.js) - Install Hook Executes Local JS File in package.json DESTINATION - 1 exfil (custom-c2) (values recorded in verified_iocs) EXFIL - OAST/Interactsh Exfiltration in beacon.js: "oast.site" ADDITIONAL FINDINGS - Publisher Has Other Malicious Packages PAYLOAD FILES beacon.js