Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@doaction/sudo-promptnpm

@doaction/sudo-prompt is a confirmed malicious npm package (MAL-2026-5380) that steals credentials and exfiltrates sensitive data (malicious versions 9.9.9, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @doaction/sudo-prompt (npm)

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

What this malware does

@doaction/sudo-prompt shares the name of the widely-used unscoped sudo-prompt package but contains none of its privilege-escalation functionality. The only behavior is environment telemetry: package.json maps preinstall to node scripts/postinstall.js, which requires @doaction/shared/bin/postinstall.js (and a sibling scripts/preinstall.js requires @doaction/shared/bin/preinstall.js); the dependency performs Datadog environment telemetry on install. The single exported function reportSudoEnv(config) in src/index.js unconditionally calls reportEnvToDatadog(...) with hardcoded service identifier doaction-sudo-prompt and tag module: sudo-prompt. Caller passes their own ddApiKey, so the destination Datadog account is caller-controlled rather than attacker-owned, and no third-party-attacker-controlled endpoint was identified. The concerns are (a) the name overlap with a popular package, which can mislead developers into installing a telemetry shim instead of the privilege-prompt library they expected, and (b) the preinstall hook performs outbound telemetry without an opt-in. There is no credential scraping, no remote code fetch, no attacker-controlled exfiltration endpoint, and no install-time destruction. Routing to human review to assess the name-confusion risk against the legitimate sudo-prompt package and the undisclosed install-time telemetry behavior.

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

2 flagged
9.9.999.99.99

Indicators of compromise (SHA-256)

488a945e315d4824a3cc9dbb099b6eb414d12692164cb2c965626725ff64776a
1083bbecb5bbb6de74ff391c8e0516c1041b464d728ff90b3727d78b7cd19e91
e989180180ebba42b05f086cda01159058a0a9ccca3c4beb95f3e5a31430dfe6

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @doaction/sudo-prompt (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @doaction/sudo-prompt across your stack and pipelines.

  2. If you installed it — respond

    @doaction/sudo-prompt 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/sudo-prompt was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @doaction/sudo-prompt before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-f9qh-hqgp-pgvcIN-MAL-2026-008115IN-MAL-2026-008983

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @doaction/sudo-prompt-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/sudo-prompt (npm) malicious package — MAL-2026-5380 | O3 Security