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

material-ui-plugin-cache-endpointnpm

Malicious code in material-ui-plugin-cache-endpoint (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2926
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall material-ui-plugin-cache-endpoint

What this malware does

The package material-ui-plugin-cache-endpoint 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 'material-ui-plugin-cache-endpoint' @ 99.9.9 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

c2bbd186eca5601f3f1cd839d7e916af5739e014ac917ef6891f0042b0678da1
45efd49ad74d002b46224881218cf53c763e58c0b71ed3d3ff3a79d1021f3a64
052e89f8cbbd6b36a7e088f0a341e529f4a28e05dd7ccfb12266f586a45f577d

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 material-ui-plugin-cache-endpoint (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging material-ui-plugin-cache-endpoint across your stack and pipelines.

  2. If you installed it — respond

    Remove material-ui-plugin-cache-endpoint 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 material-ui-plugin-cache-endpoint 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 material-ui-plugin-cache-endpoint 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. material-ui-plugin-cache-endpoint on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gcvj-xqr7-rc54

References

Credits

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

Detect & block this

O3 blocks material-ui-plugin-cache-endpoint-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.

material-ui-plugin-cache-endpoint (npm) malicious package — MAL-2026-2926 | O3 Security