nolimit-agentnpm
nolimit-agent is a confirmed malicious npm package (MAL-2026-12183) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.299, 1.0.300, 1.0.301…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nolimit-agent (npm)
What this malware does
Package is a weaponized mass-mail / SMS spam and phishing toolkit distributed as an npm package. All 45 source files under.ad/ are post-obfuscated with javascript-obfuscator (string-array + RC4 + self-defending wrappers) per its own scripts.build='node scripts/obfuscate.js' step, and package.json keywords include 'red-team' and 'smtp'. Functionality includes bulk SMTP sending, SMS sending via carrier email-gateways, scanner-evasion features (HTML-attachment redirect obfuscation via base64+JS reassembly, SVG attachments using xlink:href,.url file gateway bypass), open-redirect scanning, and DKIM key generation (templates/functions.txt;.ad/x0.js). A nolimit auth google|microsoft / nolimit contacts flow in.ad/x12.js performs device-code OAuth against Microsoft (hardcoded Azure client_id 9e5f94bc-e8a4-4e73-b8be-63364c29d753) and Google, then enumerates Microsoft Graph endpoints (/me/contacts, /me/people, /me/messages, /me/mailFolders/sentitems/messages) and the Google People API (people/me/connections) to extract the operator's contact list and prior-recipient addresses for use as spam/phishing targets; OAuth tokens are written to local smtps.txt and are not relayed to the author. A license check in.ad/x4.js POSTs {key, hwid, hostname, platform} to http://api.nolimitent.xyz:4100/api/verify and /api/activate over plain HTTP. The Windows-only postinstall (scripts/postinstall.js) is a benign bin-shim creator with no network I/O. The package does not exfiltrate the installer's secrets or run attacker code on install; instead, installing and running it turns the installer's machine and accounts into an instrument for outbound abuse against third parties, with obfuscation specifically engineered to defeat registry scanning.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nolimit-agent (47 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nolimit-agent across your stack and pipelines.
If you installed it — respond
nolimit-agent 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 nolimit-agent 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 nolimit-agent 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks nolimit-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.