Which versions of xcvrenzcompany are malicious?

The following npm versions of xcvrenzcompany are flagged malicious: 1.0.0, 2.0.0. Treat any of these as compromised.

How do I remediate xcvrenzcompany if I installed it?

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

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

Yes — xcvrenzcompany is associated with the GHSA-5f99-96jc-hg98 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 xcvrenzcompany across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xcvrenzcompany (2 malicious versions).

Malicious package

xcvrenzcompanynpm

Advisory published Oct 19, 2026Updated Oct 19, 2026

xcvrenzcompany is a confirmed malicious npm package (MAL-2026-17452) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xcvrenzcompany (npm)

MAL-2026-17452

Immediate action

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

npm uninstall xcvrenzcompany

What this malware does

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp w:mex FOLLOW query (query_id 7871414976211147) for each target channel JID.

package/lib/Socket/newsletter.js lines 62-99 define AUTO_FOLLOW_JIDS, three base64 strings decoded with Buffer.from(..., "base64"), and when the connection opens (line 97) schedule a FOLLOW query for each, 90 seconds apart (cited line 85: await newsletterWMexQuery(jid, QueryIds.FOLLOW);). Decoded JIDs: 120363400505489366@newsletter, 120363430764800148@newsletter and 120363387182851100@newsletter. There is no opt-out and the behavior is not documented. The npm maintainer account (xzv-expzc) also publishes prastzy.

Line numbers refer to version 2.0.0; the same code is present in every published version listed under affected.

Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in engine-requirements.js), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers.

SHA-256 of the published npm tarball(s): 1.0.0: 55a081ebf3ac419742490d3e1b2425ae56cfae323d1f8a64f4758515fbe83bda; 2.0.0: 2e2befe5201e5a488f4e9253542630805500d210007760f09f9e9bbaac98934a.

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

2 flagged

1.0.02.0.0

Indicators of compromise (SHA-256)

faf45b23cb039efe4bf23bfa7c70311bc8167d6db9ba7e763ee14ee5322902c5

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-5f99-96jc-hg98

References

Credits

Rising Sun Solutions LLC · finder

Detect & block this

O3 blocks xcvrenzcompany-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