eka-empal64-breki has 1 version on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.
Affected versions
Check what you actually have installed with npm ls eka-empal64-breki.
Yesterday's (Sept 6) sweep captured 13 npm items; the queue then flushed ~200 more, mostly published as of 2026-09-06 and continuing into 2026-09-07. Three coherent clusters (tea.xyz eka-<indonesian-food><N>-<suffix> autopublish, tea.xyz eigenstate-<astronomy>-<tech>-<lib> autopublish, and effective_/efficient_<animal>_z3n research spam) plus a long tail of misc E-prefix drops.
Versions named here: 0.0.0
What to do if you installed one of these
Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.
Check your whole project
eka-empal64-breki is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.
Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.
