Which versions of @meziizana/frontend-logger are malicious?

The following npm versions of @meziizana/frontend-logger are flagged malicious: 10.0.0. Treat any of these as compromised.

How do I remediate @meziizana/frontend-logger if I installed it?

@meziizana/frontend-logger 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 @meziizana/frontend-logger — how do I know if it already compromised me?

If @meziizana/frontend-logger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @meziizana/frontend-logger part of a known attack campaign?

Yes — @meziizana/frontend-logger is associated with the IN-MAL-2026-009765 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 @meziizana/frontend-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @meziizana/frontend-logger (version 10.0.0).

Malicious package

@meziizana/frontend-loggernpm

Advisory published Jul 12, 2026Updated Jul 12, 2026

@meziizana/frontend-logger is a confirmed malicious npm package (MAL-2026-10208) that steals credentials and exfiltrates sensitive data (malicious version 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @meziizana/frontend-logger (npm)

MAL-2026-10208

Immediate action

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

npm uninstall @meziizana/frontend-logger

What this malware does

package.json declares a preinstall lifecycle script that runs wget against https://webhook.site/f164a383-b9e7-4379-b18c-38bf41a3c152/ with query parameters carrying the installer's username ($(whoami)), current working directory ($(pwd)), and hostname ($(hostname)). This fires automatically on npm install with no user consent and sends installer-identifying reconnaissance data to a third-party collection endpoint. webhook.site is a public request-inspection service commonly abused as a low-effort exfiltration sink; the destination is not tied to any legitimate build or install task.

Malicious versions

1 flagged

10.0.0

Indicators of compromise (SHA-256)

a7d77255cb713e19b9560cc339e937518fdbfb49ab048d9d5a65ad81c1309a9a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @meziizana/frontend-logger (version 10.0.0).
If you installed it — respond
@meziizana/frontend-logger 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 @meziizana/frontend-logger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @meziizana/frontend-logger on npm has been identified as a malicious package (version 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009765

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @meziizana/frontend-logger-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