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

sharedclassesnpm

Malicious code in sharedclasses (npm) Remove it immediately and rotate any exposed credentials.

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

What this malware does

The package sharedclasses was found to contain malicious code.

The OpenSSF Package Analysis project identified 'sharedclasses' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

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

Malicious versions

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

27bbcbda48f1ce3d094d88b990959af80ffff4fb11c662dcad442539fcb8ac9b
8165cc7e0f3aa458299c11aee3a8c5410b51315917755edc3cff461f660cb794
9d92097d15ef8e4712a31a9d8abdaecd9e1afa7d718078fda3457ed45ef6a1c6

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

  2. If you installed it — respond

    Remove sharedclasses 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 sharedclasses 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 sharedclasses 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. sharedclasses on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 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 sharedclasses-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.

sharedclasses (npm) malicious package — MAL-2026-612 | O3 Security