Which versions of tiny-folder-tree are malicious?

The following npm versions of tiny-folder-tree are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate tiny-folder-tree if I installed it?

Remove tiny-folder-tree 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 tiny-folder-tree — how do I know if it already compromised me?

If tiny-folder-tree was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tiny-folder-tree part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tiny-folder-tree (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tiny-folder-tree across your stack and pipelines.

Malicious package

tiny-folder-treenpm

tiny-folder-tree is a confirmed malicious npm package (MAL-2026-15907) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tiny-folder-tree (npm)

MAL-2026-15907

Immediate action

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

npm uninstall tiny-folder-tree

What this malware does

[email protected] declares a postinstall script (src/build.js) that runs on npm install. The script performs a DNS TXT lookup for spreadsheets-documents.com and, when the first character of the first TXT record is '1', invokes src/tools.js which issues an HTTPS request to a URL reconstructed at runtime from obfuscated numeric constants in src/const.js (base-77/base-45 encoded strings decoding to 'https' and an 'HTTPS://...' URL). The response's 'm' header is passed directly to child_process.execSync, yielding arbitrary attacker-controlled shell execution on the installer's machine. The require target for the HTTPS module and the destination URL are both reconstructed via helpers (normalize_hash / normalize_hash_map) to evade static analysis. An author-username bypass ('justin') skips execution on the author's own host, confirming the code is intended to fire on other installers rather than the maintainer.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

fb7707665659f287294c31f37c4eff9ceba537e9b54859837615929c296a9540

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tiny-folder-tree (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tiny-folder-tree across your stack and pipelines.
If you installed it — respond
Remove tiny-folder-tree 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 tiny-folder-tree was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tiny-folder-tree before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. tiny-folder-tree on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019448

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tiny-folder-tree-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