Which versions of eventea-router are malicious?

The following npm versions of eventea-router are flagged malicious: 20.2.3. Treat any of these as compromised.

How do I remediate eventea-router if I installed it?

Remove eventea-router 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 eventea-router — how do I know if it already compromised me?

If eventea-router 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 eventea-router part of a known attack campaign?

Yes — eventea-router is associated with the IN-MAL-2026-014749, GHSA-h6vh-72w4-x86w 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 eventea-router 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 eventea-router (version 20.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eventea-router across your stack and pipelines.

Malicious package

eventea-routernpm

eventea-router is a confirmed malicious npm package (MAL-2026-12374) that executes malicious code on install (malicious version 20.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eventea-router (npm)

MAL-2026-12374

Immediate action

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

npm uninstall eventea-router

What this malware does

index.js unconditionally requires vendor.js on load. vendor.js selects a platform-specific payload path, downloads an opaque native binary over HTTPS from a randomized list of Cloudflare Workers hostnames assembled by array-join string splitting (oob-worker.cf99-9b3.workers.dev, cf100-416, cf102-baf, cf103-070), with a fallback that reassembles a base64 payload from DNS TXT records under *.dl.well1.site. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe,.cache<hex>), chmod 0755'd, and spawned detached via /bin/sh -c or cmd. Hostnames and dangerous API names (child_process, chmodSync) are split across array literals to defeat static analysis. A sibling module lib/telemetry.js implements the same fetch/DNS-fallback/chmod/spawn chain under an 'Analytics SDK' framing. setup() checks DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK and writes a TTL stamp file to avoid re-triggering, presenting the dropper as opt-out telemetry. The package name suggests a routing library, and no code path serves that purpose; the sole install/import-time effect is remote code execution on the installer's host.

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

20.2.3

Indicators of compromise (SHA-256)

a8a332e38d2400d3c15f34636f55191ca61c1d52ff49fbead378b9f9239de756

612163866035962f51d1080d88707424b95754324fe4eb36442852643956e029

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 eventea-router (version 20.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eventea-router across your stack and pipelines.
If you installed it — respond
Remove eventea-router 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 eventea-router 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 eventea-router 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. eventea-router on npm has been identified as a malicious package (version 20.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014749GHSA-h6vh-72w4-x86w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eventea-router-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

Explore

All malware advisories How O3 detects malware Vulnerability database