Which versions of @malwguy/ecto-corsair-whisper-3d2a7c are malicious?

The following npm versions of @malwguy/ecto-corsair-whisper-3d2a7c are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @malwguy/ecto-corsair-whisper-3d2a7c if I installed it?

@malwguy/ecto-corsair-whisper-3d2a7c 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 @malwguy/ecto-corsair-whisper-3d2a7c — how do I know if it already compromised me?

If @malwguy/ecto-corsair-whisper-3d2a7c 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 @malwguy/ecto-corsair-whisper-3d2a7c part of a known attack campaign?

Yes — @malwguy/ecto-corsair-whisper-3d2a7c is associated with the GHSA-636m-vpq6-g454, IN-MAL-2026-006182 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 @malwguy/ecto-corsair-whisper-3d2a7c 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 @malwguy/ecto-corsair-whisper-3d2a7c (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 @malwguy/ecto-corsair-whisper-3d2a7c across your stack and pipelines.

Malicious package

@malwguy/ecto-corsair-whisper-3d2a7cnpm

Malicious code in @malwguy/ecto-corsair-whisper-3d2a7c (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5685

Immediate action

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

npm uninstall @malwguy/ecto-corsair-whisper-3d2a7c

What this malware does

On npm install, postinstall.js walks /, /app, /home, /opt, /root for files whose names match /flag|secret|env/i, reads their contents, scrapes process.env (including HOME, INIT_CWD, npm_config_registry, all env keys, and hostname), and PUTs the collected data as a YAML manifest over plaintext HTTP to the hardcoded endpoint http://154.57.164.80:30543/api/modules/ECT-987654 (and ECT-472839). The script also includes explicit anti-analysis evasion: it checks hostname/cwd/HOME/INIT_CWD against /hscan|/home/scan|scan-|sandbox/i and silently exits if a scanner-like environment is detected, and additionally gates exfiltration on the cwd containing '/app/'. Installing this package causes immediate, automatic exfiltration of installer-side credentials and secrets to attacker-controlled infrastructure.

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)

a090f653d83ea2ab89269aac4dbbb4f750f5869e4a92b37a98223a0e9b223913

2b95a5cb65b01f03aebc1ab713877cb963b5de2cb4ddc38c03cdb01a7e469144

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 @malwguy/ecto-corsair-whisper-3d2a7c (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 @malwguy/ecto-corsair-whisper-3d2a7c across your stack and pipelines.
If you installed it — respond
@malwguy/ecto-corsair-whisper-3d2a7c 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 @malwguy/ecto-corsair-whisper-3d2a7c 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 @malwguy/ecto-corsair-whisper-3d2a7c 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. @malwguy/ecto-corsair-whisper-3d2a7c 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

GHSA-636m-vpq6-g454IN-MAL-2026-006182

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @malwguy/ecto-corsair-whisper-3d2a7c-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