# MAL-2026-17699: Malicious code in @dransay/secrets (npm)


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

## What is MAL-2026-17699?

MAL-2026-17699 is a malicious package in @dransay/secrets, published on 8 Oct 2026. 

### Official description

@dransay/secrets@99.0.0 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.

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.

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

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-17699 is a malicious package: @dransay/secrets (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-17699/ (Markdown: https://insights.sbomify.com/MAL-2026-17699/index.md)
```

## Sources

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

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