Which versions of upload-to-gcp are malicious?

The following npm versions of upload-to-gcp are flagged malicious: 3.2.1. Treat any of these as compromised.

How do I remediate upload-to-gcp if I installed it?

upload-to-gcp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed upload-to-gcp — how do I know if it already compromised me?

If upload-to-gcp 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.

Is upload-to-gcp part of a known attack campaign?

Yes — upload-to-gcp is associated with the IN-MAL-2026-017973 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find upload-to-gcp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for upload-to-gcp (version 3.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upload-to-gcp across your stack and pipelines.

Malicious package

upload-to-gcpnpm

upload-to-gcp is a confirmed malicious npm package (MAL-2026-14067) that opens a backdoor for remote access (malicious version 3.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in upload-to-gcp (npm)

MAL-2026-14067

Immediate action

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

npm uninstall upload-to-gcp

What this malware does

[email protected] runs a postinstall lifecycle script on npm install that collects host identifiers (os.hostname(), process.platform, process.arch, Node version, package name, npm lifecycle event) and POSTs them to a hardcoded remote endpoint at https://z5owtt3g.instances.poc.jchunt.top/upload-to-gcp. The destination is a random-looking subdomain not associated with Google Cloud Platform or any documented first-party service, and the transmission occurs automatically at install time with no opt-in and no disclosure. The package name suggests a GCP upload utility, which is inconsistent with the observed beaconing behavior to an unrelated host.

Malicious versions

1 flagged

3.2.1

Indicators of compromise (SHA-256)

4094f90a9780964738c1b9aea702c5554c802fba03f1a7e28c0703531dd04590

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for upload-to-gcp (version 3.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upload-to-gcp across your stack and pipelines.
If you installed it — respond
upload-to-gcp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If upload-to-gcp 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.
How O3 protects you
O3 blocks upload-to-gcp 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. upload-to-gcp on npm has been identified as a malicious package (version 3.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017973

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks upload-to-gcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database