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

aven_sharednpm

aven_shared is a confirmed malicious npm package (MAL-2026-11243) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aven_shared (npm)

MAL-2026-11243
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall aven_shared

What this malware does

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

017a3ba314e321dcd3e3b054cec53a6be0352881d36eeec79f166fe583e14f9f

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

  2. If you installed it — respond

    Remove aven_shared 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 aven_shared 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 aven_shared 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. aven_shared on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3cf3-mf4x-c7p2

References

Detect & block this

O3 blocks aven_shared-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.

Explore

aven_shared (npm) malicious package — MAL-2026-11243 | O3 Security