NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.See O3 CBOM
@egencia
The @egencia scope on npm published 8 malicious packages. See the full package list, affected versions, and how to check whether your dependency tree pulled any of them in.
Malicious packages
8
Advisories
8
Ecosystem
npm
First seen
2026-09-22
What to do if you depend on any of these
Every package below was published as malicious under @egencia. 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 @egencia rather than checking a single package name.
All 8 packagesnpm
- @egencia/design-tokensView advisory →
- @egencia/uitk-global-stylesView advisory →
- @egencia/uitk-global-styles-6View advisory →
- @egencia/uitk-reactView advisory →
- @egencia/uitk-react-foundationView advisory →
- @egencia/uitk-react-layout-flexView advisory →
- @egencia/uitk-react-spacingView advisory →
- @egencia/uitk-react-textView advisory →