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

malaganpm

Advisory published Updated

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

Malicious code in malaga (npm)

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

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)

6612dda5b3741c03f5dbad6cc253f3a6d622d30bebfd72a02ceef57826c470e4

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for malaga (all published versions).

  2. If you installed it — respond

    Remove malaga 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 malaga 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. malaga 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-7pm8-488h-944p

References

Detect & block this

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

malaga (npm) malicious package — MAL-2026-20237 | O3 Security