# MAL-2026-5378: Malicious code in @doaction/signalhub (npm)


- **Type:** Malicious package
- **Package:** `@doaction/signalhub` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-gq53-mvg2-fxjf

## What is MAL-2026-5378?

MAL-2026-5378 is a malicious package in @doaction/signalhub, published on 9 Jun 2026. 

### Official description

@doaction/signalhub@9.9.9 is shaped as a dependency-confusion attack against organizations using a private @doaction scope. package.json declares `"preinstall": "node scripts/postinstall.js"`, which unconditionally `require()`s `@doaction/shared/bin/postinstall.js`. The package's own src/index.js re-exports `collectEnv`, `sendToDatadog`, and `reportEnvToDatadog` from @doaction/shared, and the description states the purpose is "Datadog environment telemetry for internal testing." On `npm install`, before any user code runs, the preinstall hook executes and ships the installer's environment variables to a third-party Datadog endpoint with no consent prompt and no opt-out. The 9.9.9 version on a scoped, internal-sounding name is the canonical dependency-confusion squat marker — designed to outrank private-registry versions and silently resolve from the public registry into internal builds.

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-5378?

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

## Sources

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

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