Which versions of @cloudsop/hmoment are malicious?

Every published version of @cloudsop/hmoment on npm is considered malicious. Remove the package entirely.

How do I remediate @cloudsop/hmoment if I installed it?

Remove @cloudsop/hmoment 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.

I already installed @cloudsop/hmoment — how do I know if it already compromised me?

If @cloudsop/hmoment 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.

How do I find @cloudsop/hmoment across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @cloudsop/hmoment (all published versions).

Malicious package

@cloudsop/hmomentnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

@cloudsop/hmoment is a confirmed malicious npm package (MAL-2026-2408) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @cloudsop/hmoment (npm)

MAL-2026-2408

Immediate action

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

npm uninstall @cloudsop/hmoment

What this malware does

Malicious package due to suspicious install script attempting to require the current directory and low project popularity.

The package @cloudsop/hmoment was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

ad95ef51ef99f49ca08b99a81d6a18ecb75dafb1dad2afc2bca687f221ef95dc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @cloudsop/hmoment (all published versions).
If you installed it — respond
Remove @cloudsop/hmoment 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.
Did it already run?
If @cloudsop/hmoment 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. @cloudsop/hmoment on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @cloudsop/hmoment-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database