Which versions of camelot-ammv2-periphery are malicious?

The following npm versions of camelot-ammv2-periphery are flagged malicious: 1.0.0, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate camelot-ammv2-periphery if I installed it?

camelot-ammv2-periphery 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 camelot-ammv2-periphery — how do I know if it already compromised me?

If camelot-ammv2-periphery 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 camelot-ammv2-periphery part of a known attack campaign?

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

Malicious packageDiscovered by O3 Security

camelot-ammv2-peripherynpm

camelot-ammv2-periphery is a confirmed malicious npm package (MAL-2026-13773) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in camelot-ammv2-periphery (npm)

MAL-2026-13773

Immediate action

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

npm uninstall camelot-ammv2-periphery

What this malware does

camelot-ammv2-periphery is a malicious npm package that impersonates Camelot DEX's AMM v2 periphery contracts. It carries no legitimate functionality; the published tarball contains only a package.json and an install-time payload (index.js). Both preinstall and postinstall run node index.js || true, so the code executes automatically when the package is installed.

Version 1.1.0, published roughly 2.5 hours after 1.0.0 for all six packages within the same ~9-second window, reads full file contents (up to 4000 bytes) instead of just listing them. New targets include .aws/credentials, .aws/config, .ssh/id_rsa, .ssh/id_ed25519, .ssh/config, .kube/config, .docker/config.json, .netrc, .pgpass, .pypirc, .git-credentials, and two GCP credential files (application_default_credentials.json and legacy_credentials) — the ~/.config/gcloud directory listing is still collected too. It also reads local .env, .env.local, .env.production, .env.development, and secrets.env files from the working directory, and adds cryptocurrency wallet theft: key files from Solana, Anchor, NEAR, and Sui wallet paths, plus the first three files under ~/.foundry/keystores. The credential regex gains BEARER, API, INFURA, ALCHEMY, HELIUS, QUICKNODE, ANKR, and PRIVATE_KEY to catch RPC and API provider tokens. Both versions exfiltrate to the same webhook.site endpoint.

In 1.0.0, index.js opens with a fake comment claiming it is @plumenetwork/nest-artifacts, an unrelated install-time shim — @plumenetwork/nest-artifacts is not itself a malicious package, just a leftover label from whatever template the attacker reused across this batch, published by npm account mssjeep843. The fake comment was removed in 1.1.0. Five sibling packages from the same account impersonate Euler's EVC, Aerodrome Finance, Camelot AMM, and the BoringVault pattern, sharing this same webhook.site endpoint, byte-identical payload template, and 1.0.0-to-1.1.0 escalation. Two further packages from the same account (PyPI dlmm and dlmm-sdk, impersonating Meteora's DLMM SDK) ran an equivalent harvester and are tracked separately as MAL-2026-13728 and MAL-2026-13729.

Any environment that installed either version should rotate the exposed secrets and treat harvested keys as compromised, prioritizing wallet private keys and RPC/API tokens if 1.1.0 was installed.

The package impersonates the Camelot AMM v2 periphery contracts but ships only a ~~3KB Node stealer (index.js) that runs via preinstall/postinstall lifecycle hooks. On install, index.js reads well-known installer secret files (~~/.aws/credentials, ~/.aws/config, ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.kube/config, ~/.docker/config.json, ~/.netrc, ~/.npmrc, ~/.pypirc, ~/.gitconfig, ~/.git-credentials, gcloud/solana/anchor/sui/foundry keystores, and.env* files in cwd) and enumerates process.env, selecting variables whose names match /KEY|TOKEN|SECRET|PASS|PRIVATE|MNEMONIC|RPC|AWS|GITHUB|NPM|.../i. The harvested payload is POSTed to https://webhook.site/326b0891-2093-4800-a4c1-686ce3e07b09 from a detached child node process (spawn(process.execPath,['-e',src],{detached:true,stdio:'ignore'}); ch.unref()) after a randomized 60–240 second delay to outlive the install window. Execution is gated by anti-analysis checks that bail out on hostnames matching scan-/detonation/sandbox/ubuntu-fc-uvm, users scan/nonroot/sandbox, env markers honey/canarytokens/spoonfed, and mirror registries like npmmirror. No Solidity or AMM code is present; the package name and description are a lure targeting Camelot DEX integrators who hold wallet keys and RPC credentials.

Malicious versions

3 flagged

1.0.01.1.01.1.1

Indicators of compromise (SHA-256)

b2b8cdfd0d623c7f35c2c7f9ef3d8b47dc6bce534ae0ff2f230381cf151a1b2c

03a1781a084e6fad5552392169f445098b2c6c3ae5f776d47eca23269eabce73

c836be7f10db15ed9d94a06cc708ba000bd585d7b7464cd57ba042d4e10f6967

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

Campaign

IN-MAL-2026-017444IN-MAL-2026-017435IN-MAL-2026-017454

References

Credits

Amazon Inspector · finder
O3 Security · finder
SafeDep · finder

Detect & block this

O3 blocks camelot-ammv2-periphery-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