Which versions of accounts-forms are malicious?

The following npm versions of accounts-forms are flagged malicious: 0.0.2, 33.2.6. Treat any of these as compromised.

How do I remediate accounts-forms if I installed it?

accounts-forms 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 accounts-forms — how do I know if it already compromised me?

If accounts-forms 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 accounts-forms part of a known attack campaign?

Yes — accounts-forms is associated with the IN-MAL-2026-014556, IN-MAL-2026-014546 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 accounts-forms 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 accounts-forms (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging accounts-forms across your stack and pipelines.

Malicious package

accounts-formsnpm

accounts-forms is a confirmed malicious npm package (MAL-2026-12133) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.2, 33.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in accounts-forms (npm)

MAL-2026-12133

Immediate action

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

npm uninstall accounts-forms

What this malware does

On require() of accounts-forms, index.js loads polyfill.js which selects a platform-specific URL and downloads an opaque binary over HTTPS from hardcoded Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback under *.dl.well1.site. The downloaded bytes are written to a hidden path in /tmp (as.cache<hex>) or %TEMP% (as dotnet_diag_<hex>.exe or analytics_state), chmod 0755 on POSIX, and spawned detached via /bin/sh -c or cmd /c start. Destination hostnames are split across array-joined string fragments to evade static analysis, and the dropped binary uses cover-story filenames mimicking diagnostics/analytics artifacts. An opt-out gate keyed on generic telemetry environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) further disguises the fetch-and-execute chain as telemetry. The fetched executable is unsigned, unversioned, unrelated to any documented package purpose, and delivers attacker-controlled code to the installer's host on load.

Malicious versions

2 flagged

0.0.233.2.6

Indicators of compromise (SHA-256)

bc4d8be7b3e360413a04c895b17353dc61276c737614c629341c547f5b3c7bd9

f17174f805fda0f57e8b471b2a788e92836a2c20d5da22e818ed43218503b0ed

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

Campaign

IN-MAL-2026-014556IN-MAL-2026-014546

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks accounts-forms-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