<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recruitment Scams on SPERIXLABS</title><link>https://sperixlabs.org/tags/recruitment-scams/</link><description>Recent content in Recruitment Scams on SPERIXLABS</description><generator>Hugo</generator><language>en-us</language><copyright>SPERIXLABS</copyright><lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sperixlabs.org/tags/recruitment-scams/index.xml" rel="self" type="application/rss+xml"/><item><title>Fake recruitment, remote JSON payloads, and function-inliner malware (analysis)</title><link>https://sperixlabs.org/post/2026/05/fake-recruitment-remote-json-payloads-and-function-inliner-malware-analysis/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://sperixlabs.org/post/2026/05/fake-recruitment-remote-json-payloads-and-function-inliner-malware-analysis/</guid><description>&lt;p&gt;Recruiters who ask you to clone a repository and run setup scripts are not always recruiters. One common pattern is remote configuration: staged JavaScript arrives as JSON from a paste-style host, heavily obfuscated, then executes in a local Node environment with full access to the machine.&lt;/p&gt;
&lt;p&gt;This walkthrough covers two related samples (&lt;code&gt;payload.json&lt;/code&gt; at 69,459 bytes and &lt;code&gt;payload_2.json&lt;/code&gt; at 20,461 bytes), where they were fetched from, how to pull them safely for study, and what static analysis suggests they do: function-inliner obfuscation, persistence, browser credential targeting, and HTTP callback traffic.&lt;/p&gt;</description></item></channel></rss>