NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

superlib_ex3npm

Advisory published Updated

superlib_ex3 is a confirmed malicious npm package (MAL-2026-19149) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in superlib_ex3 (npm)

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

What this malware does

Malicious package. superlib_ex3 is a multi-stage loader: on install it fetches and executes a second-stage payload from the attacker-controlled host x.exxcube.fr (the install hook was observed in dynamic detonation retrieving https://x.exxcube.fr/postInstall). No legitimate functionality; all published versions are malicious. Full indicators at the reference below.

superlib_ex3 advertises itself as a trivial hello-world library exposing a single hello() function, but its npm postinstall lifecycle hook performs an unconditional network fetch to the hardcoded URL https://x.aaaaa.fr/postInstall and writes the response bytes to ./postInstall.sh in the installer's current working directory. The destination host is unrelated to the package name, has no connection to any declared publisher, and the download is unpinned, unversioned, and lacks any hash or signature verification. The fetched content is a shell script staged under a filename that collides with lifecycle-script semantics on the installer's machine. The package has no documented reason to perform network I/O or stage shell scripts, and the fetched bytes can be changed by the operator of x.aaaaa.fr at any time without any change to the published package.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

5fa6a2432d3194ebabd3d10ea038edcfd249547597ff6d02ba4754e51e545c71
bd1ec5b1f032d6879c69671f7c67499798ca134a341c87d69d310e2a36c6603b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for superlib_ex3 (2 malicious versions).

  2. If you installed it — respond

    Remove superlib_ex3 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 superlib_ex3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. superlib_ex3 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022747IN-MAL-2026-022748

References

Credits

  • Amazon Inspector · finder
  • wormsign · finder

Detect & block this

O3 blocks superlib_ex3-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

superlib_ex3 (npm) malicious package — MAL-2026-19149 | O3 Security