Which versions of accounts-constants are malicious?

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

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

Remove accounts-constants 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.

I already installed accounts-constants — how do I know if it already compromised me?

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

Yes — accounts-constants is associated with the IN-MAL-2026-014555, IN-MAL-2026-014550 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-constants 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-constants (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-constants across your stack and pipelines.

Malicious package

accounts-constantsnpm

accounts-constants is a confirmed malicious npm package (MAL-2026-12131) that executes malicious code on install (malicious versions 0.0.2, 33.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in accounts-constants (npm)

MAL-2026-12131

Immediate action

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

npm uninstall accounts-constants

What this malware does

On require of the package, index.js loads helpers.js, which selects a platform-specific endpoint from a list of Cloudflare Workers hosts assembled by joining string fragments (oob-worker.cf10-3-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT chunked-base64 fallback under *.dl.well1.site whose domain labels are also reconstructed from split arrays. The fetched binary is written to /var/tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0o755'd, and spawned detached via spawn("/bin/sh", ["-c", <path>+" &"], {detached:true}).unref() or the cmd equivalent. There is no hash or signature verification of the downloaded bytes, the endpoints are attacker-controlled Cloudflare Workers hosts unrelated to any declared publisher, and the package's stated purpose ("accounts constants wrapper") does not involve any native binary. Additional anti-analysis behavior includes a fake env-var opt-out (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK), an mtime staleness marker gating re-execution, and stderr silencing.

Malicious versions

2 flagged

0.0.233.1.7

Indicators of compromise (SHA-256)

4f43fcf66944e40e1f9523d2462f76bb9eb107b7100747d90d26a8081945c21c

b71ef624b0206201b243cfed88cdfc36804bbfd903f60cb7c9da9cfa64b4b2a7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for accounts-constants (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-constants across your stack and pipelines.
If you installed it — respond
Remove accounts-constants 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 accounts-constants 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-constants 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-constants on npm has been identified as a malicious package (versions 0.0.2, 33.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014555IN-MAL-2026-014550

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks accounts-constants-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database