Which versions of f0-form-manipulator are malicious?

The following npm versions of f0-form-manipulator are flagged malicious: 28.0.0. Treat any of these as compromised.

How do I remediate f0-form-manipulator if I installed it?

f0-form-manipulator 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 f0-form-manipulator — how do I know if it already compromised me?

If f0-form-manipulator 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 f0-form-manipulator part of a known attack campaign?

Yes — f0-form-manipulator is associated with the GHSA-r235-8hvg-777j, IN-MAL-2026-011117 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 f0-form-manipulator 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 f0-form-manipulator (version 28.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging f0-form-manipulator across your stack and pipelines.

Malicious package

f0-form-manipulatornpm

f0-form-manipulator is a confirmed malicious npm package (MAL-2026-11060) that steals credentials and exfiltrates sensitive data (malicious version 28.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in f0-form-manipulator (npm)

MAL-2026-11060

Immediate action

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

npm uninstall f0-form-manipulator

What this malware does

On npm install, the package's preinstall hook executes index.js, which collects host identifiers (os.hostname, os.platform, os.arch, os.homedir, dns.getServers) and POSTs them as JSON to a hardcoded Burp Collaborator subdomain at v62io3r4g3itdnqjg9h9pnh2mtslge43.oastify.com/hit. The exfiltration fires automatically without user interaction and reveals internal hostnames, platform details, and DNS configuration of any machine that installs the package. Behavior and naming are consistent with a dependency-confusion callback beacon.

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 'f0-form-manipulator' @ 28.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

28.0.0

Indicators of compromise (SHA-256)

e78bd44b3fd8116ff604f6faacbbf84e80c45af83fc6493040a20dd96a1eaa93

b44787fd6b711e395dc87ae7f5235d0e80d5591a925f9149319aa7d6ba3f0f72

058782981a80d3fc90af74a840a00cefa0c58b9861c481d0444b7f4f3e6a014b

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 f0-form-manipulator (version 28.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging f0-form-manipulator across your stack and pipelines.
If you installed it — respond
f0-form-manipulator 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 f0-form-manipulator 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 f0-form-manipulator 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. f0-form-manipulator on npm has been identified as a malicious package (version 28.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r235-8hvg-777jIN-MAL-2026-011117

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks f0-form-manipulator-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