Which versions of permcarmserver are malicious?

The following npm versions of permcarmserver are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate permcarmserver if I installed it?

permcarmserver carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed permcarmserver — how do I know if it already compromised me?

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

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

Malicious package

permcarmservernpm

permcarmserver is a confirmed malicious npm package (MAL-2026-10488) that runs destructive / sabotage code (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in permcarmserver (npm)

MAL-2026-10488

Immediate action

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

npm uninstall permcarmserver

What this malware does

On require, index.js spawns a worker that uses koffi FFI to load a file named index.html and invoke its exported vserver_start(). Despite the extension, index.html is an aarch64 Linux ELF shared library built from vless_ws.c; it implements a VLESS-over-WebSocket proxy with a hardcoded client UUID 4916e0f5-8abc-4ad4-ba5d-158582c60d85, accepts WebSocket upgrades, and relays arbitrary attacker-directed TCP CONNECT traffic through the installing host. The ELF returns a decoy ':: SYSTEM ONLINE:: MINECRAFT SERVER' HTML page to casual HTTP probes as a cover story. One second after the worker signals 'started', index.js recursively deletes the installed package directory with fs.rmSync(pkgDir, { recursive: true, force: true }), while the loaded native library keeps running in memory. The combination of native ELF masquerading as HTML, FFI load on require, hardcoded VLESS identity, TCP relay capability, and post-activation self-deletion converts the installing host into a covert attacker-controlled proxy relay.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4e70168ba32f543c08a0c98b81e648d09e9793bcc533a34c2f0ce9ca7a14536e

eb118ea65e8282507841d64134b4523588457ac3bd3ba4b6d3e36f97fe24bd99

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for permcarmserver (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging permcarmserver across your stack and pipelines.
If you installed it — respond
permcarmserver carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If permcarmserver 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 permcarmserver 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. permcarmserver on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010310GHSA-9499-pgrg-v7w7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks permcarmserver-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