# MAL-2026-6572: Malicious code in rebrandly-domains-digger (npm)


- **Type:** Malicious package
- **Package:** `rebrandly-domains-digger` (npm)
- **Published:** 29 Jun 2026
- **Also known as:** GHSA-44wx-4683-p2h3

## What is MAL-2026-6572?

MAL-2026-6572 is a malicious package in rebrandly-domains-digger, published on 29 Jun 2026. 

### Official description

The package declares a `preinstall` hook that runs `node callback.js`. On `npm install`, `callback.js` collects installer-side identifiers — `os.hostname()`, `os.userInfo().username`, `process.cwd()`, the configured npm registry, and CI repo-identifying environment variables (e.g. GITHUB_REPOSITORY) — and issues an HTTP GET to `http://75.119.137.232:31337/depconfuse?pkg=...` carrying those values as query parameters. The version number `9999.0.0` and the `/depconfuse` path are consistent with a dependency-confusion reconnaissance beacon designed to identify organizations that internally use a package named `rebrandly-domains-digger`, so the attacker can target follow-on confusion attacks against their private/internal package namespace. The destination is a hardcoded bare IPv4 on a non-standard port over plain HTTP, with no relation to any legitimate publisher infrastructure.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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-6572 is a malicious package: rebrandly-domains-digger (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-6572/ (Markdown: https://insights.sbomify.com/MAL-2026-6572/index.md)
```

## Sources

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

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