# MAL-2026-17697: Malicious code in @dransay/logger (npm)


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

## What is MAL-2026-17697?

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

### Official description

@dransay/logger@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 @dransay/logger@99.0.0 ships a preinstall hook (`node beacon.js`) that fires on `npm install`. The script performs a DNS lookup and HTTPS GET to the interactsh collaborator host `db3klhbi6i9hark1kegg174t38h33b6wt.oast.site`, encoding the package name in the subdomain/path. The version number (99.0.0) is implausibly high for a package with no release history, consistent with a dependency-confusion squat intended to win semver resolution against a private internal name. On install, the beacon discloses the installer's source IP, DNS resolver, and timestamp to a third-party host under the scoped name `@dransay/logger`, confirming successful resolution of this public package in an environment that may have intended to resolve a private `@dransay/*` package. No further payload is executed in this version, but the install-time callback to an attacker-controlled OAST endpoint is the reconnaissance stage of a dependency-confusion attack.

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

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

## Sources

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

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