Which versions of toll_free are malicious?

The following npm versions of toll_free are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate toll_free if I installed it?

toll_free establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed toll_free — how do I know if it already compromised me?

If toll_free 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 toll_free part of a known attack campaign?

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

Malicious package

toll_freenpm

toll_free is a confirmed malicious npm package (MAL-2026-11159) that opens a backdoor for remote access (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in toll_free (npm)

MAL-2026-11159

Immediate action

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

npm uninstall toll_free

What this malware does

package.json declares both preinstall and postinstall lifecycle hooks that run curl against a hardcoded webhook.site endpoint, sending the installer's username ($(whoami)), hostname ($(hostname)), current working directory ($PWD), and timestamp as query parameters. This fires automatically on npm install, before any code the installer intended to run. webhook.site is a third-party HTTP inspection service used to collect arbitrary request data; the specific endpoint ID is controlled by whoever created it. There is no legitimate functionality shipped with the package that would explain this beacon.

The OpenSSF Package Analysis project identified 'toll_free' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

c9425400cf10e0c56db46cd60b243224e5a7c2b63b89f4a97063346bbcc79966

80914891625809e622f8383e3d7f39792cc850a57dba2d68f831ada91cfd5871

517b4b730525b8edcc11052acd0ad205b63c60f9009f97531df84eea39eaca97

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for toll_free (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging toll_free across your stack and pipelines.
If you installed it — respond
toll_free establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If toll_free 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 toll_free 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. toll_free on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011127IN-MAL-2026-017670

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks toll_free-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database