# MAL-2026-17700: Malicious code in dransay (npm)


- **Type:** Malicious package
- **Package:** `dransay` (npm)
- **Published:** 8 Oct 2026

## What is MAL-2026-17700?

MAL-2026-17700 is a malicious package in dransay, published on 8 Oct 2026. 

### Official description

dransay@99.0.0 is a dependency-confusion probe for an internal unscoped `dransay` package name, 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 `dransay-unscoped` in the request; npm account `0xamino_hunter` published it on 2026-10-08.

dransay@99.0.0 declares a `preinstall` lifecycle script that runs `node beacon.js`, which performs a DNS lookup and HTTPS GET against a hardcoded Interactsh (`oast.site`) collaborator subdomain (`db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`) on every `npm install`. The outbound request discloses the installer's source IP, DNS resolver IP, hostname-derived data, and timestamp to a third-party collaborator host unrelated to any first-party publisher. The package name and implausibly high version (99.0.0) are consistent with a dependency-confusion probe targeting an internal package name. The README self-labels the package as a benign dependency-confusion proof-of-concept; the self-label does not change the behavior — install-time, non-consensual outbound network I/O to a researcher-controlled OAST host that collects installer network identity.

## What should I do about MAL-2026-17700?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17700 is a malicious package: dransay (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17700/ (Markdown: https://insights.sbomify.com/MAL-2026-17700/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17700

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17700/
Summaries are generated and may contain mistakes; the official description above is the record.