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

frank-research-poc-applenpm

frank-research-poc-apple is a confirmed malicious npm package (MAL-2026-3081) that executes malicious code on install (malicious version 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frank-research-poc-apple (npm)

MAL-2026-3081
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall frank-research-poc-apple

What this malware does

The package frank-research-poc-apple 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 'frank-research-poc-apple' @ 1.1.4 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
1.1.4

Indicators of compromise (SHA-256)

7f21864e3fd8ae5f8a1fe5a450428e5cd85f5b8b9bbfccb98c1fc6000a283982
216e5eb321826d85c29f23b333d509a469f138b5317a41b818da919bc9bf9c47
932979c4e7dfe11d0ae4af80eec82a7cc8da35b96030d7bc3b7f4847223f65e7

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

  2. If you installed it — respond

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

Campaign

GHSA-78hq-gp8w-grwp

References

Credits

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

Detect & block this

O3 blocks frank-research-poc-apple-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

frank-research-poc-apple (npm) malicious package — MAL-2026-3081 | O3 Security