fb-cards-form-no-resident-informationnpm
fb-cards-form-no-resident-information is a confirmed malicious npm package (MAL-2026-12178) that steals credentials and exfiltrates sensitive data (malicious version 20.4.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fb-cards-form-no-resident-information (npm)
What this malware does
On require() of the package, index.js loads adapter.js which reconstructs Cloudflare Workers hostnames from split string fragments (e.g. 'oob-worker' + '.cf101-a' + 'df.workers.dev') and downloads a platform-specific binary via https.get. A DNS TXT resolver fallback against subdomains of dl.well1.site retrieves a base64-chunked payload across numbered subdomains as an out-of-band channel. The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache<rnd>, dotnet_diag_<rnd>.exe), chmod 0755, and spawned detached via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or spawn('cmd',...). No hash or signature verification is performed; the destinations are unrelated to the package's stated purpose and are not publisher-owned infrastructure. An opt-out environment variable check is present as a cover story.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fb-cards-form-no-resident-information (version 20.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fb-cards-form-no-resident-information across your stack and pipelines.
If you installed it — respond
fb-cards-form-no-resident-information 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 fb-cards-form-no-resident-information 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 fb-cards-form-no-resident-information 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
Detect & block this
O3 blocks fb-cards-form-no-resident-information-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.