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

alimama-minisitenpm

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

Malicious code in alimama-minisite (npm)

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

What this malware does

package.json declares a self-named dependency alimama-minisite whose value is the off-registry URL https://repo.securityctrl.com/alimama-minisite instead of a semver range from the npm registry. On npm install, npm fetches whatever bytes that host returns and installs them, executing any lifecycle scripts contained in the fetched artifact. The dependency is unpinned and has no integrity check, so the returned content can change at any time. The dependency key equals the package's own name (dependency-confusion shape), and an implausibly high version (45.0.0) is set to win resolution against an internal package of the same name. The shipped index.js is an inert stub; the manifest line is the entire installer-side effect.

Malicious versions

1 flagged
45.0.0

Indicators of compromise (SHA-256)

e3efd48d631afe828271bb266e4ddb8f2f6d0a8305294f56bde57d614c1cbfef

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-019079

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks alimama-minisite-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

alimama-minisite (npm) malicious package — MAL-2026-15495 | O3 Security