NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

mayx-blognpm

Advisory published Updated

mayx-blog is a confirmed malicious npm package (MAL-2026-20296) that executes malicious code on install (malicious versions 0.0.0-g0938411, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mayx-blog (npm)

MAL-2026-20296
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mayx-blog

What this malware does

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
0.0.0-g09384111.0.0

Indicators of compromise (SHA-256)

7bc3e579802686dee8fa199060a018f109b73dd07fd1ed2b9156b189ebdbcff4
a8d20971dbd37897fbdfbb932da94ef3866aa1f2c3e31f0161d29d0edf9f2ea4

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for mayx-blog (2 malicious versions).

  2. If you installed it — respond

    Remove mayx-blog from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If mayx-blog 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. mayx-blog on npm has been identified as a malicious package (versions 0.0.0-g0938411, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gmwr-j73c-6xw3

References

Detect & block this

O3 blocks mayx-blog-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

mayx-blog (npm) malicious package — MAL-2026-20296 | O3 Security