eventea-diag (npm) · Malicious Code
Affects eventea-diagSource GCVE Database
Malicious package : remove eventea-diag and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12373
What to do
Remove eventea-diag from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmeventea-diag | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9941ff32c3b2d52ea7b7cccd4af391bfe359cf3766c4f22c484d1a51e178ab6c) On require of the package, index.js loads _shim.js which downloads a platform-specific binary from hardcoded Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT base64 fallback to dl.well1.site, writes the bytes to a hidden temp file, chmods 755, and spawns it detached via /bin/sh -c or cmd. Host strings and dangerous APIs are assembled from split fragments at runtime (e.g. ["oob-worker.cf102-baf",".w","or","ke","rs",".d","ev"].join(""), require("child_"+"process"), fs["chmod"+"Sync"]) to hide the destinations and primitives from static analysis. Cover-story naming (analytics_state, dotnet_diag_*.exe,.cache_*) does not match the package's stated pub/sub adapter purpose. A second dropper implementation with the same pattern is bundled as lib/telemetry.js (81KB) framed as an 'Analytics SDK'. There is no pinning, no signature verification, and the delivery hosts are anonymous Cloudflare Workers subdomains unrelated to any declared publisher. ## Source: ghsa-malware (f50f3b0e728e475ae1632ffe36294b2f132bd392b3f8878fe8b7f1a5627ccd08) 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.