Which versions of @osmura/treeify are malicious?

The following npm versions of @osmura/treeify are flagged malicious: 1.1.2, 1.1.3. Treat any of these as compromised.

How do I remediate @osmura/treeify if I installed it?

@osmura/treeify is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @osmura/treeify — how do I know if it already compromised me?

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

Yes — @osmura/treeify is associated with the IN-MAL-2026-007673, IN-MAL-2026-007672 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 @osmura/treeify 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 @osmura/treeify (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @osmura/treeify across your stack and pipelines.

Malicious package

@osmura/treeifynpm

Malicious code in @osmura/treeify (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6542

Immediate action

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

npm uninstall @osmura/treeify

What this malware does

The package republishes the upstream treeify library (Luke Plaster, repo notatestuser/treeify) verbatim under the unrelated @osmura scope, preserving the original package.json author/repository/keywords/README as cover. Appended to treeify.js (starting around line 115) is ~93KB of obfuscator.io-style code (RC4+base64 string-array, while(!![]) control-flow flattening) that runs whenever a consumer does require('@osmura/treeify'). The injected code re-spawns Node detached with a marker environment variable, issues an HTTPS request to a hostname encoded inside the obfuscated string array, AES-256-GCM-decrypts the response using a key XOR-derived from four embedded base64 buffers, writes the plaintext payload into os.tmpdir()/<name>-<pid>/, and spawns it via child_process.spawn(..., {stdio:..., windowsHide: true, detached: true}) — see treeify.js:116 var aM = at[ba(0x19,...)](aK, aL, {'stdio':..., 'windowsHide':!![], 'detached':!![]}) and the corresponding https.request({method: 'GET', hostname: aG[...], timeout: 60000},...) call. Two independent injected IIFEs implement the same dropper with separate encoded URL pools, providing fallback C2. Any installer that requires this package fetches and executes attacker-controlled code on their machine at import time.

Malicious versions

2 flagged

1.1.21.1.3

Indicators of compromise (SHA-256)

4643c1f27e4916ea6090f1e6196c980fa1d65b96899a80b1f57633eaf16a61a9

ff88024c29a68b4dc5e73795a21a813393c8a6a56cfbef9c8a0950a63ec84256

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @osmura/treeify (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @osmura/treeify across your stack and pipelines.
If you installed it — respond
@osmura/treeify is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @osmura/treeify 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 @osmura/treeify 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. @osmura/treeify on npm has been identified as a malicious package (versions 1.1.2, 1.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007673IN-MAL-2026-007672

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @osmura/treeify-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring