Which versions of message-compiler are malicious?

The following npm versions of message-compiler are flagged malicious: 9.2.0. Treat any of these as compromised.

How do I remediate message-compiler if I installed it?

message-compiler 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 message-compiler — how do I know if it already compromised me?

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

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

Malicious package

message-compilernpm

message-compiler is a confirmed malicious npm package (MAL-2026-14392) that steals credentials and exfiltrates sensitive data (malicious version 9.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in message-compiler (npm)

MAL-2026-14392

Immediate action

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

npm uninstall message-compiler

What this malware does

The package declares scripts.preinstall = 'node vishu.js', which runs automatically on npm install. vishu.js resolves the installer's public IP via api.ipify.org, reads CI-related environment variables (CI, GITHUB_ACTIONS, GITHUB_WORKFLOW, GITHUB_RUN_ID and related), and issues an HTTPS GET to a hardcoded webhook.site collector URL carrying those fields. It additionally performs a DNS lookup of a subdomain constructed from os.hostname() under a hardcoded oastify.com (Burp Collaborator) domain, exfiltrating the installer's hostname via DNS. The package name typosquats the scoped @intlify/message-compiler package and its only functional code is this beacon.

Malicious versions

1 flagged

9.2.0

Indicators of compromise (SHA-256)

f7469b2a666f71db1dd06fd00d6ae630becf97ad6854ff5c8938d2adcb5c8417

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

Campaign

IN-MAL-2026-018616

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks message-compiler-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