joko-keripik55-sluey has 1 version on the npm registry flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories.
joko-keripik55-sluey was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.
Affected versions
Check what you actually have installed with npm ls joko-keripik55-sluey.
GHSA 2026-09-13/14: PyPI chroma-client extends the 2026-09-openaii typosquat wave (chromadb typosquat, same infostealer+cryptominer payload as openaii/langgrap/transfomers/ollamaa); PyPI python-fork is a plain import-time fork bomb; npm job-iteration flagged as CWE-506 malware. Otherwise the day is a massive tea.xyz autopublish spam wave — hundreds of joko-{Indonesian food}-{suffix} names sourced from joan-teadev/joknmax autopublish scripts, plus joint_*_z3n/joint_*_0xrequest continuation of the 2026-09-11 family_*_z3n operator and joker123/joker388 casino-themed spam.
Versions named here: *
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
joko-keripik55-sluey 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.
