<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: social-engineering</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/social-engineering.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2026-04-03T13:54:53+00:00</updated><author><name>Simon Willison</name></author><entry><title>The Axios supply chain attack used individually targeted social engineering</title><link href="https://simonwillison.net/2026/Apr/3/supply-chain-social-engineering/#atom-tag" rel="alternate"/><published>2026-04-03T13:54:53+00:00</published><updated>2026-04-03T13:54:53+00:00</updated><id>https://simonwillison.net/2026/Apr/3/supply-chain-social-engineering/#atom-tag</id><summary type="html">
    &lt;p&gt;The Axios team have published a &lt;a href="https://github.com/axios/axios/issues/10636"&gt;full postmortem&lt;/a&gt; on the supply chain attack which resulted in a malware dependency going out &lt;a href="https://simonwillison.net/2026/Mar/31/supply-chain-attack-on-axios/"&gt;in a release the other day&lt;/a&gt;, and it involved a sophisticated social engineering campaign targeting one of their maintainers directly. Here's Jason Saayman'a description of &lt;a href="https://github.com/axios/axios/issues/10636#issuecomment-4180237789"&gt;how that worked&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;so the attack vector mimics what google has documented here: &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/unc1069-targets-cryptocurrency-ai-social-engineering"&gt;https://cloud.google.com/blog/topics/threat-intelligence/unc1069-targets-cryptocurrency-ai-social-engineering&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;they tailored this process specifically to me by doing the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;they reached out masquerading as the founder of a company they had cloned the companys founders likeness as well as the company itself.&lt;/li&gt;
&lt;li&gt;they then invited me to a real slack workspace. this workspace was branded to the companies ci and named in a plausible manner. the slack was thought out very well, they had channels where they were sharing linked-in posts, the linked in posts i presume just went to the real companys account but it was super convincing etc. they even had what i presume were fake profiles of the team of the company but also number of other oss maintainers.&lt;/li&gt;
&lt;li&gt;they scheduled a meeting with me to connect. the meeting was on ms teams. the meeting had what seemed to be a group of people that were involved.&lt;/li&gt;
&lt;li&gt;the meeting said something on my system was out of date. i installed the missing item as i presumed it was something to do with teams, and this was the RAT.&lt;/li&gt;
&lt;li&gt;everything was extremely well co-ordinated looked legit and was done in a professional manner.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;A RAT is a Remote Access Trojan - this was the software which stole the developer's credentials which could then be used to publish the malicious package.&lt;/p&gt;
&lt;p&gt;That's a &lt;em&gt;very effective&lt;/em&gt; scam. I join a lot of meetings where I find myself needing to install Webex or Microsoft Teams or similar at the last moment and the time constraint means I always click "yes" to things as quickly as possible to make sure I don't join late.&lt;/p&gt;
&lt;p&gt;Every maintainer of open source software used by enough people to be worth taking in this way needs to be familiar with this attack strategy.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/packaging"&gt;packaging&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-engineering"&gt;social-engineering&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/supply-chain"&gt;supply-chain&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="open-source"/><category term="packaging"/><category term="security"/><category term="social-engineering"/><category term="supply-chain"/></entry><entry><title>Apple just gave out my Apple ID password because someone asked</title><link href="https://simonwillison.net/2008/Jul/8/apple/#atom-tag" rel="alternate"/><published>2008-07-08T10:10:25+00:00</published><updated>2008-07-08T10:10:25+00:00</updated><id>https://simonwillison.net/2008/Jul/8/apple/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.karppinen.fi/2008/07/apple-just-gave-out-my-apple-i.html"&gt;Apple just gave out my Apple ID password because someone asked&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
“am forget my password of mac,did you give me password on new email marko.[redacted] @yahoo.com”. Classy.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apple"&gt;apple&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-engineering"&gt;social-engineering&lt;/a&gt;&lt;/p&gt;



</summary><category term="apple"/><category term="security"/><category term="social-engineering"/></entry><entry><title>Social engineering and Orange</title><link href="https://simonwillison.net/2005/Nov/9/orange/#atom-tag" rel="alternate"/><published>2005-11-09T20:52:12+00:00</published><updated>2005-11-09T20:52:12+00:00</updated><id>https://simonwillison.net/2005/Nov/9/orange/#atom-tag</id><summary type="html">
    &lt;p id="p-0"&gt;I had a call on my mobile earlier today from a lady claiming to be from &lt;a href="http://www.orange.co.uk/"&gt;Orange&lt;/a&gt; (my phone service provider) who told me that my contract was about to expire. She asked me for my password.&lt;/p&gt;

&lt;p id="p-1"&gt;Alarm bells instantly went off in my head, so I told her (truthfully as it happens) that I didn't know my password. Then she asked for my postcode instead.&lt;/p&gt;

&lt;p id="p-2"&gt;At this point I was pretty sure this was a social engineering attack, so I started to quiz her about why she needed the information. She said it was for a "security check". I told her I was uncomfortable giving out information like this to a cold caller over the phone and she said it was nothing to worry about because it was all covered by "the data protection act".&lt;/p&gt;

&lt;p id="p-3"&gt;I said that I would rather conduct my business in an Orange shop, and she told me that she would have to put a mark on my record that I had failed a security check. I interpreted this as a threat, which convinced me that the call was an attempted con. I asked for her name and ended the call.&lt;/p&gt;

&lt;p id="p-4"&gt;I e-mailed Orange customer support via &lt;a href="http://www.orange.co.uk/contact/" title="Orange Customer Service"&gt;their website&lt;/a&gt; with details of the call and the number it came from (07973 100 194, which looked like a mobile number to me and had further fuelled my suspicions). I just received their reply - the call really was from them!&lt;/p&gt;

&lt;p id="p-5"&gt;Banks and other online services have learnt to repeatedly tell their customers that they will &lt;em&gt;never&lt;/em&gt; contact them and ask for their password. Orange are leaving themselves wide open to &lt;a href="http://en.wikipedia.org/wiki/Social_engineering_%28computer_security%29"&gt;social engineering&lt;/a&gt; attacks. This incredible lack of attention to basic security has given me serious second thoughts about trusting them with my business at all.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/orange"&gt;orange&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-engineering"&gt;social-engineering&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="orange"/><category term="security"/><category term="social-engineering"/></entry></feed>