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

apple-mycelium-fixnpm

apple-mycelium-fix is a confirmed malicious npm package (MAL-2026-3416) that executes malicious code on install (malicious versions 1.2.1778333524, 1.8.1778336376). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in apple-mycelium-fix (npm)

MAL-2026-3416
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall apple-mycelium-fix

What this malware does

The package apple-mycelium-fix 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.

The OpenSSF Package Analysis project identified 'apple-mycelium-fix' @ 1.2.1778333524 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
1.2.17783335241.8.1778336376

Indicators of compromise (SHA-256)

a64eb5f60a8d57bd23e8b18ceeea76083900d2400329d2e68d47e5264e6d76ab
fddb6b83974fb63a902bbe0142a427575ff562f4d741ac48ea35fbb9d195b105
e69a2534c8bb0842243808b87451a399a8fc121ee56e755a33627f21035f8e33
b50cf3ede15485f8c375bb271e52389f7688f6fff125ad74596d8c58eb820217

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

  2. If you installed it — respond

    Remove apple-mycelium-fix 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 apple-mycelium-fix 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 apple-mycelium-fix 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. apple-mycelium-fix on npm has been identified as a malicious package (versions 1.2.1778333524, 1.8.1778336376 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fjcr-w74v-m2qw

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks apple-mycelium-fix-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

apple-mycelium-fix (npm) malicious package — MAL-2026-3416 | O3 Security