Summary
Togoder Security scanned the npm package from2@2.3.0 on Oct 6, 2026. An AI review of 2 source files produced 2 low severity findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 2
File System Write/Delete in Tests
NPS-8A97C19499A8
The test writes to a temporary file 'tmp.txt' in the same directory and then deletes it. This is typical test behavior and not malicious, but it does modify the file system within the package directory.
File System Write/Delete in Tests
NPS-CAF18FA72699
The test deletes the temporary file 'tmp.txt' after reading it. This is typical test behavior and not malicious.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | Cleared by Jev triage; no further analysis needed |
| test.js | safe | The code is a test file for the 'from2' package and contains only standard test operations with no malicious patterns. |
Frequently asked questions
Is from2 safe to use?
Our AI source review of from2@2.3.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does from2 contain malware?
No malware was identified in from2@2.3.0 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was from2 checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan from2 together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in from2@2.3.0, cost nothing.