@public-for-cdao
The @public-for-cdao scope on npm published 15 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 @public-for-cdao. 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 @public-for-cdao rather than checking a single package name.
- @public-for-cdao/abiView advisory →
- @public-for-cdao/apiView advisory →
- @public-for-cdao/backendView advisory →
- @public-for-cdao/botView advisory →
- @public-for-cdao/commonView advisory →
- @public-for-cdao/configView advisory →
- @public-for-cdao/contractsView advisory →
- @public-for-cdao/coreView advisory →
- @public-for-cdao/deployView advisory →
- @public-for-cdao/hooksView advisory →
- @public-for-cdao/sdkView advisory →
- @public-for-cdao/signerView advisory →
- @public-for-cdao/tokenView advisory →
- @public-for-cdao/typesView advisory →
- @public-for-cdao/utilsView advisory →