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

@automagik/genienpm

Malicious code in @automagik/genie (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2992
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @automagik/genie

What this malware does

The package @automagik/genie was found to contain malicious code.

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

11 flagged
4.260421.334.260421.344.260421.354.260421.364.260421.374.260421.384.260421.394.260421.404.260422.14.260422.24.260422.3

Indicators of compromise (SHA-256)

00207299cc0b9ee634f5850f194f399c6164fd4621989a43f8e5f9353d3707ac
3a6e7702eae0e8ff480f6f47624128cb3bf2ad5934d6c6a9a5481f3ac424db40

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

  2. If you installed it — respond

    Remove @automagik/genie 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 @automagik/genie 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 @automagik/genie 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. @automagik/genie on npm has been identified as a malicious package (versions 4.260421.33, 4.260421.34, 4.260421.35, 4.260421.36, 4.260421.37, 4.260421.38, 4.260421.39, 4.260421.40, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ppw4-42v6-538v

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @automagik/genie-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.