Malicious code in @dransay/api (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

@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. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e237d11d4a80279031cdf312f3c879913d5ce485a74538e52b64a03a4332da34) @dransay/[email protected] is a dependency-confusion-shaped package (unscoped-sounding name with an implausibly high version 99.0.0 and publishConfig public) whose package.json declares a preinstall script `node beacon.js`. On every `npm install`, beacon.js performs a DNS lookup and HTTPS GET to a hardcoded Interactsh out-of-band collaborator host `db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`, with the package name included in the DNS label and HTTP path. This causes the installer's source IP, resolver IP, install timestamp, and the fact that the internal package name resolved against the public npm registry to be transmitted to a third-party OOB server. The pattern is consistent with a dependency-confusion probe: a package name chosen to collide with a target organization's internal package is published to the public registry at a very high version so that a misconfigured internal resolver pulls the public copy, and the preinstall beacon then signals the attacker that the confusion succeeded. No further payload is shipped in this version, but the install-time outbound call to an attacker-controlled OOB host occurs without installer opt-in and leaks installer-identifying information.

Source published

8 Oct 2026 07:58:05 UTC

Source modified

12 Oct 2026 14:30:19 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.