# MAL-2026-12178: Malicious code in fb-cards-form-no-resident-information (npm)


- **Type:** Malicious package
- **Package:** `fb-cards-form-no-resident-information` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-5gv5-4q77-jc7x

## What is MAL-2026-12178?

MAL-2026-12178 is a malicious package in fb-cards-form-no-resident-information, published on 5 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-12178?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12178 is a malicious package: fb-cards-form-no-resident-information (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12178/ (Markdown: https://insights.sbomify.com/MAL-2026-12178/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12178

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12178/
Summaries are generated and may contain mistakes; the official description above is the record.