Which versions of accounts-appointment are malicious?

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

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

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

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

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

Malicious package

accounts-appointmentnpm

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

Malicious code in accounts-appointment (npm)

MAL-2026-12129

Immediate action

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

npm uninstall accounts-appointment

What this malware does

index.js unconditionally requires./setup, which on load selects a platform-specific payload path, fetches bytes over HTTPS from Cloudflare workers.dev subdomains (oob-worker.cf99-9b3.workers.dev and siblings cf100-416/cf101-adf/cf103-070.workers.dev) with a DNS TXT-record fallback channel under *.dl.well1.site, writes the payload to /var/tmp or %TEMP% under decoy names resembling.NET diagnostic files (.cache_<hex> / dotnet_diag_<hex>.exe), chmods 0755 on unix, and spawns the file detached via /bin/sh -c or cmd.exe /c start. Endpoint hostnames are assembled via array-join string concatenation to evade static string search, and a secondary DNS TXT loader queries c.<domain> for a chunk count and reassembles base64 chunks from N.<domain> TXT records. The dropper fires on any require/import of the package and executes attacker-controlled code on the installer's host.

Malicious versions

2 flagged

0.0.233.2.6

Indicators of compromise (SHA-256)

12cacc35ffc7d789f337229c235e234a9f6ac6f18d6ed1f30fa4024c0ea15d22

b85924ae1e24ede2acf333de8af5ca1d8ae2854652be2b3b82a01df710adc27a

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-appointment (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-appointment across your stack and pipelines.
If you installed it — respond
Remove accounts-appointment 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-appointment 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-appointment 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-appointment 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-014552IN-MAL-2026-014557

References

Credits

Amazon Inspector · finder

Detect & block this

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