Which versions of @depup/memfs are malicious?

The following npm versions of @depup/memfs are flagged malicious: 4.67.0-depup.0. Treat any of these as compromised.

How do I remediate @depup/memfs if I installed it?

@depup/memfs is a typosquat — you almost certainly intended a legitimately-named package. Remove @depup/memfs, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @depup/memfs — how do I know if it already compromised me?

If @depup/memfs 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 @depup/memfs part of a known attack campaign?

Yes — @depup/memfs is associated with the IN-MAL-2026-017132 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 @depup/memfs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @depup/memfs (version 4.67.0-depup.0).

Malicious package

@depup/memfsnpm

Advisory published Aug 7, 2026Updated Aug 7, 2026

@depup/memfs is a confirmed malicious npm package (MAL-2026-13624) that typosquats a legitimate package to trick installs (malicious version 4.67.0-depup.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @depup/memfs (npm)

MAL-2026-13624

Immediate action

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

npm uninstall @depup/memfs

What this malware does

This package is an automated 'DepUp' republish of memfs whose lib/index.js and lib/index.d.ts have been stripped of the upstream source and rewritten to require nine '@jsonjoy.com/fs-' packages (fs-node, fs-core, fs-node-utils, fs-fsa, fs-node-to-fsa, fs-fsa-to-node, fs-print, fs-snapshot, fs-node-builtins), all pinned to 4.67.0 — a version tag that matches memfs itself rather than any real release history of those names. Upstream memfs bundles its own source and does not depend on these packages. The republished lib/index.js contains only require() calls to the '@jsonjoy.com/fs-' names, so installing this package and importing memfs resolves and executes whatever code is published under those names at 4.67.0. The package.json 'depup.changes' metadata also records bumping @jsonjoy.com/json-pack and @jsonjoy.com/util from ^1.11.0/^1.9.0 to ^18.28.0, non-contiguous jumps well beyond the real published range of those libraries, consistent with steering the resolver toward attacker-published versions. Installing or requiring @depup/memfs pulls in and runs code from a set of newly-introduced dependency names controlled by the republisher, with no lifecycle hook needed — a dependency-chain dropper shape via a memfs lookalike.

Malicious versions

1 flagged

4.67.0-depup.0

Indicators of compromise (SHA-256)

267188642a5aa8db495698be0d44bd4fed45e0e247572d44da6b76e3d1b72a5e

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @depup/memfs (version 4.67.0-depup.0).
If you installed it — respond
@depup/memfs is a typosquat — you almost certainly intended a legitimately-named package. Remove @depup/memfs, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @depup/memfs 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. @depup/memfs on npm has been identified as a malicious package (version 4.67.0-depup.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017132

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @depup/memfs-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