@s4yhiitestpoc
The @s4yhiitestpoc scope on npm published 12 malicious packages. See the full package list, affected versions, and how to check whether your dependency tree pulled any of them in.
What to do if you depend on any of these
Every package below was published as malicious under @s4yhiitestpoc. Treat any machine that installed one as compromised: remove the package and its lockfile entry, rotate every credential the build or runtime could reach (registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values) from a known-clean machine, and audit for unexpected outbound activity.
Because the packages share a publisher scope, a project that pulled in one has an elevated chance of having pulled in others. Search your lockfiles for @s4yhiitestpoc rather than checking a single package name.
- @s4yhiitestpoc/r2-controlView advisory →
- @s4yhiitestpoc/r2-dnsView advisory →
- @s4yhiitestpoc/r2-echoView advisory →
- @s4yhiitestpoc/r2-httpsView advisory →
- @s4yhiitestpoc/r2-https-bView advisory →
- @s4yhiitestpoc/r2-https-dualuseView advisory →
- @s4yhiitestpoc/r3-httpsView advisory →
- @s4yhiitestpoc/scan-control-aView advisory →
- @s4yhiitestpoc/scan-dns-cView advisory →
- @s4yhiitestpoc/scan-echo-bView advisory →
- @s4yhiitestpoc/scan-https-dView advisory →
- @s4yhiitestpoc/scan-https-dualuse-eView advisory →