Which versions of momenntjs are malicious?

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

How do I remediate momenntjs if I installed it?

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

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

Yes — momenntjs is associated with the IN-MAL-2026-010518 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 momenntjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for momenntjs (version 1.0.0).

Malicious package

momenntjsnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

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

Malicious code in momenntjs (npm)

MAL-2026-10588

Immediate action

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

npm uninstall momenntjs

What this malware does

momenntjs is a typosquat of momentjs whose package.json postinstall hook runs node.init.js. On npm install,.init.js enumerates roughly 60 credential-shaped environment variables (including NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, STRIPE_, DB_PASSWORD, SSH_KEY, GCP/AZURE/Cloudflare tokens, and TWINE credentials) and reads home-directory credential files including ~/.npmrc, ~/.env, config/credentials.json, and files under ~/.config matching token/cred/secret patterns. It also collects host identifiers (os.hostname(), os.platform(), process.cwd(), process.pid) and POSTs the combined JSON payload to a hardcoded webhook.cool inbox at tender-deer-80. The package provides no legitimate functionality matching its name.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6aae445dd0b77bd7409820067097404e4ccb16d658e7911c7c4e659146fdfad4

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-010518

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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