NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @doaction published 15 malicious packages. See the full campaign →
Malicious package

@doaction/signalhubnpm

Advisory published Updated

@doaction/signalhub is a confirmed malicious npm package (MAL-2026-5378) that steals credentials and exfiltrates sensitive data (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @doaction/signalhub (npm)

MAL-2026-5378
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @doaction/signalhub

What this malware does

@doaction/[email protected] 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.

Malicious versions

1 flagged
9.9.9

Indicators of compromise (SHA-256)

26d01f70e44bfde852833da7b4f06378079149fd4de4541f91fb8a4f1423b5c7
f7bca1eff18553fad58ccd2097810887a61afc717b44a657c6674bfa7317bb41
62b531b4b8b72408146b3eb732cdb15803a8a8d33aa6ef56fa3194c1e8572637

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @doaction/signalhub (version 9.9.9).

  2. If you installed it — respond

    @doaction/signalhub is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @doaction/signalhub was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @doaction/signalhub on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gq53-mvg2-fxjfIN-MAL-2026-005183IN-MAL-2026-005184

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @doaction/signalhub-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@doaction/signalhub (npm) malicious package — MAL-2026-5378 | O3 Security