Which versions of functions-framework-nodejs are malicious?

The following npm versions of functions-framework-nodejs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate functions-framework-nodejs if I installed it?

functions-framework-nodejs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed functions-framework-nodejs — how do I know if it already compromised me?

If functions-framework-nodejs 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 functions-framework-nodejs part of a known attack campaign?

Yes — functions-framework-nodejs is associated with the IN-MAL-2026-017653 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 functions-framework-nodejs 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 functions-framework-nodejs (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging functions-framework-nodejs across your stack and pipelines.

Malicious package

functions-framework-nodejsnpm

functions-framework-nodejs is a confirmed malicious npm package (MAL-2026-13951) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in functions-framework-nodejs (npm)

MAL-2026-13951

Immediate action

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

npm uninstall functions-framework-nodejs

What this malware does

Package functions-framework-nodejs is a typosquat of Google's @google-cloud/functions-framework. Its package.json declares postinstall: node install.js, and install.js runs execSync("id") on the installer's host, then POSTs the captured Unix user/group identity (with package name, version, and timestamp) to a hardcoded webhook.site collector URL. The advertised library surface (index.js) is a trivial stub exporting only name and version — the package's sole functional effect on install is the identity exfiltration. Package metadata self-labels as "For Security Research" by author "Berserk"; that label does not change the behavior: on npm install, installer-side host identity is sent to a third-party endpoint the installer did not configure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d4c9e327ae7e806fc6d270807180963349c0b7578b69f31336780d87323fdafa

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for functions-framework-nodejs (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging functions-framework-nodejs across your stack and pipelines.
If you installed it — respond
functions-framework-nodejs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If functions-framework-nodejs 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 functions-framework-nodejs 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. functions-framework-nodejs on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017653

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks functions-framework-nodejs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database