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

@mimecast-ui/componentsnpm

Malicious code in @mimecast-ui/components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3507
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mimecast-ui/components

What this malware does

The package @mimecast-ui/components was found to contain malicious code.

The OpenSSF Package Analysis project identified '@mimecast-ui/components' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
2.0.0

Indicators of compromise (SHA-256)

a8bd78a0c0e2baca560a44d5047bc0414e53cea80e7a97f0d37a109025bba99f
7e59a7d55636b02d0a28954889c22f021de5b4f33c525ce7712706df60cd9af3

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

  2. If you installed it — respond

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

Credits

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

Detect & block this

O3 blocks @mimecast-ui/components-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.