Which versions of messenger-style are malicious?

The following npm versions of messenger-style are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate messenger-style if I installed it?

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

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

Yes — messenger-style is associated with the IN-MAL-2026-014966, RLMA-2026-10760 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 messenger-style across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for messenger-style (version 1.0.1).

Malicious package

messenger-stylenpm

Advisory published Aug 5, 2026Updated Sep 24, 2026

messenger-style is a confirmed malicious npm package (MAL-2026-12796) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in messenger-style (npm)

MAL-2026-12796

Immediate action

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

npm uninstall messenger-style

What this malware does

The package's preinstall hook runs node index.js, which collects host identifiers (os.hostname(), os.userInfo().username, home directory, DNS servers) and reads /etc/passwd and /etc/hosts from the installer's machine, then POSTs the collected data over HTTPS to the hardcoded host pkdzrreksftymvx4d0o5olnxiooic80x.oastify.com (a Burp Collaborator out-of-band interaction domain). The package name suggests a messaging utility, but no such functionality is present — the sole behavior on npm install is host reconnaissance and exfiltration to an attacker-controlled OAST endpoint.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

48e89235ade6dcbf682edae5afb7d789c6a834b2ebe032fac72c796734837d10

5d3ef8925eb477ec2e943816f1ac33ced93d62e2bcf7119ec51f3403357ba85a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for messenger-style (version 1.0.1).
If you installed it — respond
messenger-style 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 messenger-style 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. messenger-style on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014966RLMA-2026-10760

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks messenger-style-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