Which versions of @frengki0707/google-cloud-clone are malicious?

The following npm versions of @frengki0707/google-cloud-clone are flagged malicious: 1.33.1. Treat any of these as compromised.

How do I remediate @frengki0707/google-cloud-clone if I installed it?

Remove @frengki0707/google-cloud-clone 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.

I already installed @frengki0707/google-cloud-clone — how do I know if it already compromised me?

If @frengki0707/google-cloud-clone 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.

How do I find @frengki0707/google-cloud-clone across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @frengki0707/google-cloud-clone (version 1.33.1).

Malicious package

@frengki0707/google-cloud-clonenpm

Advisory published Apr 24, 2026Updated Apr 30, 2026

@frengki0707/google-cloud-clone is a confirmed malicious npm package (MAL-2026-3060) that executes malicious code on install (malicious version 1.33.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @frengki0707/google-cloud-clone (npm)

MAL-2026-3060

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @frengki0707/google-cloud-clone

What this malware does

The package @frengki0707/google-cloud-clone was found to contain malicious code.

The OpenSSF Package Analysis project identified '@frengki0707/google-cloud-clone' @ 1.33.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged

1.33.1

Indicators of compromise (SHA-256)

4d0d989816aabe2e23e707e43df34ae454a644ee62730252f5967448420f5a17

a278202a1e4a54c185b707e1eeed0b0df0438168bcec4a2a5b5741bcbd8a5e5c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @frengki0707/google-cloud-clone (version 1.33.1).
If you installed it — respond
Remove @frengki0707/google-cloud-clone 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.
Did it already run?
If @frengki0707/google-cloud-clone 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. @frengki0707/google-cloud-clone on npm has been identified as a malicious package (version 1.33.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @frengki0707/google-cloud-clone-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database