Which versions of account-merge-site are malicious?

The following npm versions of account-merge-site are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate account-merge-site if I installed it?

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

If account-merge-site was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find account-merge-site across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for account-merge-site (2 malicious versions).

Malicious package

account-merge-sitenpm

Advisory published Oct 30, 2025Updated Sep 21, 2026

account-merge-site is a confirmed malicious npm package (MAL-2025-49107) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in account-merge-site (npm)

MAL-2025-49107

Immediate action

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

npm uninstall account-merge-site

What this malware does

The package account-merge-site was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

e9da6b4c4378cd7eac26edb573618fc697b4312cfef6741c25ceb45871856fad

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for account-merge-site (2 malicious versions).
If you installed it — respond
Remove account-merge-site 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 account-merge-site was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. account-merge-site on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks account-merge-site-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