Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

experian-design-systemnpm

Malicious code in experian-design-system (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-282
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall experian-design-system

What this malware does

The package experian-design-system was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'experian-design-system' @ 99.99.1 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
99.99.1

Indicators of compromise (SHA-256)

629f30cfc3fe4cc45698b5cce11973037d0fa7f6564fc999aef0247701f6fee5
6b0c3bb14a927ee9e0596747365d1fd1f996ac21a4b3558ac8863007d33ec811
67a3825abd28507cc227c0126793dce0989a61b295f1f772639e6daf5bba55c1

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for experian-design-system (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging experian-design-system across your stack and pipelines.

  2. If you installed it — respond

    Remove experian-design-system from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If experian-design-system was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks experian-design-system before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. experian-design-system on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jvff-mx8m-g6wr

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks experian-design-system-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

experian-design-system (npm) malicious package — MAL-2026-282 | O3 Security