MAL-2026-17696

    Dashboard / Malicious Package / MAL-2026-17696

    MAL-2026-17696

    Published: 8 Oct 2026Last Modified: 12 Oct 2026

    Summary: Malicious code in @dransay/feature-flags (npm)

    Details: @dransay/[email protected] is a dependency-confusion probe claiming the internal `@dransay/*` namespace, not an identified public package. Its `preinstall` hook runs on npm install as `node beacon.js` and sends a DNS lookup and an HTTPS GET to `db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`, using the package name in the request; npm account `0xamino_hunter` published it on 2026-10-08. Source: amazon-inspector (cc545bbb96903ee25218d8cab1a7d116d2ceb1ba64a3c929c79e56a6fc8e0585) @dransay/[email protected] publishes a scoped name on the public npm registry at an inflated version (99.0.0) designed to win semver resolution against any private internal @dransay/* copy. package.json declares a preinstall hook `node beacon.js`; beacon.js unconditionally performs a DNS lookup and HTTPS GET to the hardcoded interactsh callback host db3klhbi6i9hark1kegg174t38h33b6wt.oast.site on every `npm install`, leaking the installer's public source IP, a timestamp, and confirmation that the scoped name resolved from the public registry to a third-party out-of-band interaction collector. The README self-describes the artifact as a probe of DrAnsay build infrastructure; author self-labeling as research does not change the install-time behavior for any environment whose npm resolves @dransay/* publicly.

    References: https://www.npmjs.com/package/@dransay/feature-flags/v/99.0.0, https://www.npmjs.com/package/@dransay/feature-flags

    Affected packages

    Package

    Name: @dransay/feature-flags

    Purl: pkg:npm/%40dransay/feature-flags

    Affected ranges

    Type: N/A

    Events:

    Introduced- None
    Fixed -None

    Affected versions

    99.0.0