NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

pure-folder-threenpm

Advisory published Updated

pure-folder-three is a confirmed malicious npm package (MAL-2026-10218) that executes malicious code on install (malicious versions 0.5.0, 0.6.0, 0.7.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pure-folder-three (npm)

MAL-2026-10218
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pure-folder-three

What this malware does

[email protected] executes attacker-controlled shell commands on install and on import. The postinstall entry (src/build.js) decodes an obfuscated destination via base-45/base-77 fromCharCode arithmetic, resolving to https://rnjkerbf.org/T/ with process.platform appended, and dynamically resolves require('https') through the same decoder. It issues an https request to that host and passes the response's m header directly to child_process.execSync, giving the remote server arbitrary command execution on the installer host. The payload is gated by a username check that skips execution when USER/LOGNAME/USERNAME contains 'justin', excluding the author's own machine while running on every other installer. The same chain is also reachable at require/import time: src/index.js imports './build.js' from the package main, so consumers that load the module trigger the fetch-and-exec chain even with npm install --ignore-scripts. The URL, hostname, and the 'https' module name are all reconstructed from numeric arrays, concealing the network destination and the execution sink.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

5 flagged
0.5.00.6.00.7.00.7.10.7.3

Indicators of compromise (SHA-256)

887e7a8ffa4cbf636ad2fbeddbcdde33aa6a325c9e033561009be3e1095001d3
6e83bf74d7c84c48a1a478d7bb40bbd899c4fda613f1512b66184d3de478b480

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for pure-folder-three (5 malicious versions).

  2. If you installed it — respond

    Remove pure-folder-three 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.

  3. Did it already run?

    If pure-folder-three 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. pure-folder-three on npm has been identified as a malicious package (versions 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.7.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9w58-3cgj-jw7vIN-MAL-2026-009788

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks pure-folder-three-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.

Explore

pure-folder-three (npm) malicious package — MAL-2026-10218 | O3 Security