Which versions of totally-safe-util are malicious?

Every published version of totally-safe-util on npm is considered malicious. Remove the package entirely.

How do I remediate totally-safe-util if I installed it?

Remove totally-safe-util 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 totally-safe-util — how do I know if it already compromised me?

If totally-safe-util 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 totally-safe-util across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for totally-safe-util (all published versions).

Malicious package

totally-safe-utilnpm

Advisory published Apr 6, 2026Updated Apr 7, 2026

totally-safe-util is a confirmed malicious npm package (MAL-2026-2500) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in totally-safe-util (npm)

MAL-2026-2500

Immediate action

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

npm uninstall totally-safe-util

What this malware does

Multiple suspicious behaviors: postinstall script, hex obfuscation, OS command execution to open a Rickroll, and attempt to hide execution.

The package totally-safe-util 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)

0d45a8a1395a8ff66e2ea74cacd9d8de0ebaa9e88e0170a6907b3e4861a2acc5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for totally-safe-util (all published versions).
If you installed it — respond
Remove totally-safe-util 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 totally-safe-util 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. totally-safe-util 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 totally-safe-util-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