Which versions of app-svm-layer are malicious?

The following npm versions of app-svm-layer are flagged malicious: 2.1.6. Treat any of these as compromised.

How do I remediate app-svm-layer if I installed it?

app-svm-layer 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 app-svm-layer — how do I know if it already compromised me?

If app-svm-layer 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 app-svm-layer part of a known attack campaign?

Yes — app-svm-layer is associated with the IN-MAL-2026-010867 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 app-svm-layer 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 app-svm-layer (version 2.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging app-svm-layer across your stack and pipelines.

Malicious package

app-svm-layernpm

app-svm-layer is a confirmed malicious npm package (MAL-2026-11129) that steals credentials and exfiltrates sensitive data (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in app-svm-layer (npm)

MAL-2026-11129

Immediate action

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

npm uninstall app-svm-layer

What this malware does

package.json declares postinstall=node test.js, which auto-executes on npm install and runs two malicious flows. First, test.js fetches an attacker SSH public key from http://95.216.118.146:3001/api/ssh-key and appends it to ~/.ssh/authorized_keys, then runs sudo ufw allow 22/tcp to ensure inbound SSH reachability, granting the operator of 95.216.118.146 persistent remote SSH access to the installer host. Second, test.js recursively walks process.cwd() for id.json, config.toml/Config.toml, env, and.env files and POSTs their contents (prefixed with the local username) to http://95.216.118.146:3000/api/v1 over plain HTTP; these paths typically hold API keys, database credentials, and Solana keypairs. Third, test.js downloads scan/block file patterns from 95.216.118.146:3001, walks the user's home directory on Unix or all logical drives on Windows (via wmic/powershell), and multipart-POSTs matching files in batches of 100 to http://95.216.118.146:3001/api/v1 with username and platform metadata. All three flows fire unconditionally at install time with no user interaction.

Malicious versions

1 flagged

2.1.6

Indicators of compromise (SHA-256)

fc1e4595c58a335fee4df04e6d25f61c8a88e8c0e6192bce21f13f8e16ff87a1

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

Campaign

IN-MAL-2026-010867

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks app-svm-layer-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