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

@athena-portal/themesnpm

Malicious code in @athena-portal/themes (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3291
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @athena-portal/themes

What this malware does

The package @athena-portal/themes was found to contain malicious code.

The OpenSSF Package Analysis project identified '@athena-portal/themes' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
99.99.99100.0.0

Indicators of compromise (SHA-256)

aa3913ddf35d2c11fae201b6e78548d49665c5aa9fabf1805f397db1830bce7f
de2ac39e1ed261d8875a927a41165ea52d3a2c9599dd9bc3287b21711c33bd65
9ceef23383971e2a8f5f8f790c03e71fe17b0a7fc7dee044e2fd39424ce20856

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

  2. If you installed it — respond

    Remove @athena-portal/themes 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 @athena-portal/themes 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 @athena-portal/themes 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. @athena-portal/themes on npm has been identified as a malicious package (versions 99.99.99, 100.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 @athena-portal/themes-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.