Summary
Togoder Security scanned the npm package intl-messageformat@11.2.14 on Oct 6, 2026. An AI review of 2 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | No malicious patterns detected |
| intl-messageformat.iife.js | safe | No malicious patterns detected; the code is the legitimate @formatjs/intl-messageformat library implementing ICU message parsing and formatting with no data exfiltration, credential harvesting, dynamic code execution, or other suspicious behavior. |
Scanned versions of intl-messageformat
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 11.2.14 | No issues | 2 | Oct 6, 2026 |
Frequently asked questions
Is intl-messageformat safe to use?
Our AI source review of intl-messageformat@11.2.14 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does intl-messageformat contain malware?
No malware was identified in intl-messageformat@11.2.14 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 intl-messageformat 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 intl-messageformat 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 intl-messageformat@11.2.14, cost nothing.