Togoder security

npm package security report

process-warning@1.0.0 security report

Risky patterns found that deserve a look.

Needs review Version 1.0.0 Files reviewed 3 Size 5.0 KB Scanned

Summary

Togoder Security scanned the npm package process-warning@1.0.0 on Oct 4, 2026. An AI review of 3 source files produced 2 low severity findings. The overall verdict is medium: the findings flag risky but common patterns (dynamic code, unsafe defaults, broad file or network access) rather than confirmed malware.

0
critical
0
high
0
medium
2
low

Findings 2

low

Global event listener registration

NPS-0301830BF575

The test adds listeners to process.on('warning', ...) during test execution. This is expected test behavior but demonstrates the package interacts with Node.js process-level warning events, which is the module's intended functionality rather than a malicious pattern.

test.js
low

Global side effect / event listener manipulation

NPS-F250E595CDAD

The test file calls process.removeAllListeners('warning') at module load time, which removes all existing 'warning' event listeners from the Node.js process globally. This is a side effect that occurs on import and could interfere with other modules or applications relying on warning listeners. While this is a test file and likely intentional for test isolation, it modifies global process state without user consent and is a suspicious pattern in third-party packages.

test.js:7

Files reviewed

FileVerdictWhat the reviewer saw
test.js medium This is a test file for a warning utility package that manipulates global process warning listeners at import time but contains no malicious patterns such as exfiltration, credential harvesting, or code execution.
index.js safe Cleared by Jev triage; no further analysis needed
index.test-d.ts safe Cleared by Jev triage; no further analysis needed

Affected version ranges

None of the 2 scanned versions of process-warning are flagged high or critical. The latest scanned version, 5.1.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.

1.0.05.1.0
VersionsVerdictCountRangeTop findings
5.1.0 No issues 1 5.1.0
5.0.0 Not scanned 1 5.0.0
1.0.0 Needs review 1 1.0.0

Full list, including published versions not scanned yet: version ranges API.

Scanned versions of process-warning

VersionVerdictFilesScanned
5.1.0 No issues 5 Oct 4, 2026
1.0.0 Needs review 3 Oct 4, 2026

Frequently asked questions

Is process-warning safe to use?

No confirmed malware was found in process-warning@1.0.0, but the review flagged 2 low severity findings for risky patterns worth checking before you rely on it.

Does process-warning contain malware?

No malware was identified in process-warning@1.0.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.

How was process-warning checked?

Togoder Security downloaded the published npm package and had an AI model read its 3 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 process-warning 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 process-warning@1.0.0, cost nothing.

Related security reports