Which versions of @doaction/eventemitter are malicious?

The following npm versions of @doaction/eventemitter are flagged malicious: 9.9.9, 99.99.99. Treat any of these as compromised.

How do I remediate @doaction/eventemitter if I installed it?

Remove @doaction/eventemitter from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @doaction/eventemitter — how do I know if it already compromised me?

If @doaction/eventemitter 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.

Is @doaction/eventemitter part of a known attack campaign?

Yes — @doaction/eventemitter is associated with the GHSA-926j-qqmq-889c, IN-MAL-2026-005193, IN-MAL-2026-005192, IN-MAL-2026-008110 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @doaction/eventemitter across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @doaction/eventemitter (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/eventemitter across your stack and pipelines.

Malicious package

@doaction/eventemitternpm

Malicious code in @doaction/eventemitter (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5370

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @doaction/eventemitter

What this malware does

The package is a thin shim. package.json declares preinstall: node scripts/postinstall.js, which require()s @doaction/shared/bin/preinstall.js — meaning the install-time behavior is sourced from a sibling package that is not present in this tarball. src/index.js re-exports collectEnv, sendToDatadog, and reportEnvToDatadog from @doaction/shared and offers a reportEventEnv helper that posts an EVENT_* env subset to Datadog using a caller-supplied API key (gated on explicit user invocation, not a silent relay in this package itself). Several attributes are characteristic of dependency-confusion staging: a 99.99.99 version (well above any plausible real release), an 'internal testing' description, and a scope (@doaction) that may shadow an internal namespace. The actual install-time impact depends entirely on @doaction/shared's implementation of collectEnv and the preinstall script, which cannot be confirmed from this tarball alone. Routing for human review to confirm whether @doaction/shared is attacker-controlled (dependency-confusion attack) and to assess the env-collection behavior it actually performs at install time.

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)

2cfab693f8195c9b7d400aa6bcc6db510b89cd4920bdb622cc06b369a4ed226f

356613a140f3268f2633d292a37370ac2324af412bd3dbf6be2603f426db80cf

5221b351f74900764906fd20a62e5c3f390473ed87a1d4fb781e34d3ffd2f623

865100529f6c19b1eff05a47c96abd2d4eb5dba0d4fc0af838c307c816072a20

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @doaction/eventemitter (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/eventemitter across your stack and pipelines.
If you installed it — respond
Remove @doaction/eventemitter from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @doaction/eventemitter 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.
How O3 protects you
O3 blocks @doaction/eventemitter 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/eventemitter 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-926j-qqmq-889cIN-MAL-2026-005193IN-MAL-2026-005192IN-MAL-2026-008110

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring