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

frank-bot-gogle-cloningnpm

Advisory published Updated

frank-bot-gogle-cloning is a confirmed malicious npm package (MAL-2026-3080) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frank-bot-gogle-cloning (npm)

MAL-2026-3080
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall frank-bot-gogle-cloning

What this malware does

The package frank-bot-gogle-cloning 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-bot-gogle-cloning' @ 1.1.0 (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.0

Indicators of compromise (SHA-256)

49dddf11519659e89469fd400ecad5f7975ea44b898a3cdb5647d0042168e8b7
44bf385867bdd18d9634c115e9e423146f198038e6fdb1d6dca9c95743f3af4b
e3a32293feff1ab95419661b2b8756448c3f5bc8351acbae9a5423496d7081ff

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for frank-bot-gogle-cloning (version 1.1.0).

  2. If you installed it — respond

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

Campaign

GHSA-52j3-fx2q-cqm9

References

Credits

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

Detect & block this

O3 blocks frank-bot-gogle-cloning-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-bot-gogle-cloning (npm) malicious package — MAL-2026-3080 | O3 Security